The tracker URL code also referred as LifeSight Pixel is an analytics tool that allows you to measure the effectiveness of your advertising by understanding the actions (i.e. impressions and clicks) people take on your website. You can use pixel data to make sure that your ads are being shown to the right people at the right time. The pixels are generated by LifeSight as part of attribution campaign tracking.


Pixel Versions:


LifeSight has three variants of pixels, based on the kind of attribution, and the way they are to be handled and incorporated to the ads. These variants are slightly different from each other.


  • Variant 1: Impression tracking Pixel.
  • Variant 2: Click tracking pixel without redirect.
  • Variant 3: Click tracking pixel with redirect.


Note: These pixels will be generated by LifeSight APP as shown in the figure below (figure 1) . However, configuration of the pixels, as recommended, is the responsibility of AdOps team to make seamless attribution tracking possible.



figure 1


Impression Pixel:

https://pixel.ad.lifesight.io/pixel/event/WG0S66?event=RENDER&ios_idfa=[ios_idfa]&android_gaid=[android_gaid]&cid=[campaign_id]&app=[app_name]&channel=[channel]&dnt=[do_not_track]&cb=[cache buster]&ts=[currentTime]


Click Pixel:

https://pixel.ad.lifesight.io/pixel/event/WG0S66?event=CLICK&ios_idfa=[ios_idfa]&android_gaid=[android_gaid]&cid=[campaign_id]&app=[app_name]&channel=[channel]&dnt=[do_not_track]&cb=[cachebu ster]&ts=[currentTime]&redirect=[urlencoded_redirect_url]


PARAMETER
NAME
DESCRIPTION
Mandatory? 

event


Event


Capture the event of Ad exposure


event=RENDER

event=CLICK


ios_idfa

IOS Advertising ID

Configure the ios id parameter before applying the pixel to the creative.

Yes.
param_value should be configured according to the platform where the ad runs.

android_idfa

ANDROID Advertising ID

Configure the android id parameter before applying the pixel to the creative.

Yes.
param_value should be configured according to the platform where the ad runs.

cid

Campaign ID

Enter the Campaign ID to be tracked

Placeholder parameter.


app
App Name

To get App Name from the DSP.


Yes. Configure the macro properly to get the App Name.


Channel

Channel ID

Enter the Channel ID to be tracked

Yes. Custom Value customisation.


dnt

Do not track

True/False

No. This should be substituted by the platform where the campaign runs.
Pixel will be tracked if dnt = False

ip

IP Address

System generated

No

userAgent

User Information

System generated

No

currentTime

Current System Time

System generated

No

price

Impression price

System generated based on the campaign tracker details filled

No

Redirect
Redirect URL
Landing Page URL
Landing Page URL (if needed)


Important Note:

  • The pixel provided by LifeSight has to be implemented along with the creative.
  • Fields that are marked as configured Y is to be inputted based on the campaign, so as to enable proper tracking of the attribution.
  • To track both impressions & clicks, both the pixels are to be implemented in the creatives.


LifeSight Pixel Capability Map


CHANNEL
IMPRESSIONS
CLICKS
ACTIONS
IN APP
Y
Y
NA
Mobile WEB
Y
Y
NA
Desktop
Y
Y
Y**
Paid Search
N
Y
NA
Social Media
N
Y
NA
Email
Y
N
NA
Lead Form
Y*
Y*
Y**
Landing Page
Y*
Y*
Y**
Out of Home
Y
NA
NA
Webroom
Y
Y
Y**

*  : Depends on the definition of Impression/click. We can capture the visit to the lead form/landing page. 
**This requires customisation at the customers’ end to fire LifeSight pixel with unique custom value in ‘channel’ param on the ‘ACTION’ in the web page.



LifeSight DSP Capability Map


DSP
CREATIVE
IMPRESSION
CLICKS
DBM
BANNER
Y
Y
VIDEO
Y
Y
RICH MEDIA
Y
Y
FB
BANNER
N
Y
VIDEO
N
Y
RICH MEDIA
N
Y
NATIVE
N
Y*
DFP
BANNER
Y
Y
VIDEO
Y
Y
RICH MEDIA
Y
Y
Ad Words
SEARCH
N
Y
DISPLAY
N
Y
VIDEO
N
Y
SHOPPING
N
Y
UNIVERSAL APP
NA
NA
OTHER DSPs
BANNER
Y
Y
VIDEO
Y
Y
RICH MEDIA
Y
Y



DFP Macro Customisation

PARAMETER
NAME
MACRO
event
Event
Customize:
event=RENDER
Event=CLICK
ios_idfa
IOS Advertising ID
%%ADVERTISING_IDENTIFIER_PLAIN%%
android_idfa
ANDROID Advertising ID
%%ADVERTISING_IDENTIFIER_PLAIN%%
cid
Campaign ID
%eaid!
app
App Name
[app_name]
Channel
Channel ID
Customize Channel for Custom Values.
dnt
Do not track
[dnt]
Redirect
Redirect URL
Encoded URL*


Note: Use url encoders to to encode the landing page URL. This is mandatory if you need to pass a query param to the landing page. 
Reference Link:

https://support.google.com/dfp_premium/answer/2376981?hl=en



DBM Macro Customization

PARAMETER
NAME
DESCRIPTION
To Be Configured?
event
Event
Capture the event of Ad exposure
event=RENDER
event=CLICK
Channel
Channel ID

Channel ID

Customise Channel for Custom Values.
dnt
Do not track


Redirect
Redirect URL
Redirect URL
Encoded URL*



DCM Macro Customization

PARAMETER
NAME
MACRO

event

Event

Customize:
event=RENDER
event=CLICK

ios_idfa

IOS Advertising ID

{%E}

android_idfa

ANDROID Advertising ID

{%E}

Channel

Channel ID

Customize Channel for Custom Values.

Redirect

Redirect URL

Encoded URL*



AdWords Macro Customization

PARAMETER
NAME
MACRO

event

Event

Customize:
event=CLICK

ios_idfa

IOS Advertising ID

ADVERTISING_IDENTIFIER

android_idfa

ANDROID Advertising ID

ADVERTISING_IDENTIFIER

Channel

Channel ID

Customize Channel for Custom Values.



A sample installation of Tracker (LifeSight Pixel)

  • Step 1 : Copy the pixel from the LifeSight Tracker Page.
  • Step 2 : Customise the Pixel by updating event=RENDER for impressions, event=CLICK for clicks.
  • Step 3 : Substitute DSP specific macros.
  • Step 4 : Deploy the Tracker with the creatives in DSP.



Note: Contact support@lifesight.io for any implementation related queries.