You have several options for tracking and traffic analytics in AlterCPA: UTM tags, integrations with trackers, advertising network pixels, tracking codes for analytics systems, arbitrary code on websites. There is built-in integration with Facebook, Google Analytics or Google Tag Manager, Tik-Tok, MailTarget, VK, Likee, Yandex.Metrika.
Advertising networks and analytics systems
Tracking codes and pixels are inserted into websites automatically. Pixels on all sites are dynamic: you don't have to specify the pixel ID in the flow settings, you can specify it in the GET parameter of the link to the site. They work in the same way both on sites in the repository and on sites downloaded from the flow. Depending on the network and offer, different pixels and counters may be available to you.
Some analytics systems don't send a conversion event on the Thank you page. For these counters, it is recommended to configure triggering by the presence of the text success
in the link.
On a landing or pre-landing page, the pixel sends a PageView
event. After 30 seconds of the user's stay on the site, the ViewContent
event is dispatched. On the Thank You page, the pixel dispatches the PageView
and Lead
events. Instead of the Lead
event, you can specify your own character code.
To setup the pixel, the following parameters are used:
- Facebook, parameter
fb
- Facebook pixel ID, numbers only. You can specify multiple identifiers separated by commas. Example:12345678901234
. - FB conversion event, parameter
fbe
- character code of the conversion event for the thank you page, which will be used instead ofLead
. For example:InitiateCheckout
orPurchase
. Don't enter a pixel ID here!
Facebook server pixel
The pixel fires once when a lead enters the system. Requires setting up the application and obtaining a token from Facebook.
To setup the pixel, the following parameters are used:
- Facebook S2S pixel - pixel identifier, numbers only. Only one pixel can be set, for example:
12345678901234
. - Facebook S2S event - character code of the event that will be sent with the pixel. If not specified, the
Lead
event is used. - Facebook S2S token - Facebook application token with access to sending pixels.
- Proxy for S2S request - proxy for sending pixels is specified with protocol, IP address and port, for example:
http://12.34.56.78:99
- Proxy login and password - if the proxy requires authorization, specify the proxy login and password separated by a colon, for example:
username:password
Google Analytics and Tag Manager
Tracking code from Google can be set in Google Analytics or Google Tag Manager format. If the ID starts with GTM, TagManager is used, otherwise Analytics is used.
To setup the pixel, the following parameters are used:
- Google Analytics / Tag Manager, parameter
ga
- symbolic identifier of the tag in the formAW-XXXXXXX
,GTM-XXXXXXX
and the like. - Google Analytics Conversion Event, parameter
gad
is a strange character set from analytics settings.
In the analytics event settings, you will come across a code like AW-XXXXX/abcdef12345
. The abcdef12345
piece is the event you need, specify it in the settings.
VK
The VK audience collection pixel is located on all pages of the site. Thank you page fires lead
event.
To configure, use the VK retarget field or the vk
parameter. It specifies the pixel ID, for example: VK-RTGT-XXXX-XXXX
.
Yandex.Metrika
The Yandex.Metrika counter is installed on all pages of the site. No events are sent automatically, use URL settings.
Use the Yandex.Metrika field or the mtrk
parameter to configure. It specifies the counter ID, for example: 1234567890
.
Mail Target
The Mail Target counter dispatches the PageView
event on all pages. On the "Thank you" page, the ItemView
event with the purchase
type is additionally fired.
Use the Mail Target field or the mt
parameter to configure. It specifies the counter ID, for example: 1234567890
.
Tik-Tok
The Tik-Tok pixel is installed on all pages of the site. No events are sent automatically, use URL settings.
Use the Tik-Tok field or the tt
parameter to configure. It specifies the counter ID, for example: 1234567890
.
Likee
The pixel sends a page_view
event on all pages. The Thank you page additionally sends a form
event.
Use the Likee field or the lki
parameter to configure. It specifies the counter ID, for example: 1234567890
.
Pixels in the URL
To pass counters and pixels in a link, use the parameters:
fb
- Facebook pixel ID, multiple separated by commas.fbe
- Facebook conversion event code, if you need something instead of Lead.ga
- Google Analytics or Tag Manager counter ID.gad
- symbolic identifier of the Google Analytics conversion event.vk
- VK retagret pixel ID.mtrk
- Yandex.Metrika counter ID.mt
- ID of the Mail Target counter.tt
- Tik-Tok pixel ID.lki
- Likee pixel ID.
UTM tags
You can use five standard UTM tags to track your traffic: utm_source
, utm_content
, utm_content
, utm_term
and utm_medium
. Parameters with these names can be used in any links, postback requests and APIs.
UTM tags are searchable and filterable in statistics reports and lead lists. The length of any of the labels must not exceed 255 characters. The use of UTM tags with arbitrary names is not supported.
Tags for agancies
When working as an agency, two additional tracking tags are available to you:
- Click or lead ID - a unique identifier on the side of your CRM or tracker. Passed in the
extu
parameter; when working with the API, it can be passed in theid
parameter. - ID of the source or webmaster - passed in the
exts
parameter, API can be passed in thewm
parameter.
The use of these options is not strictly required, but is highly recommended. They are displayed in the lead list and in the special "External Tags" statistics report. Unique ones are used to upload statistics and work with postbacks. Labels must not exceed 255 characters.
Tags for trackers
We offer three additional tags that you can use to integrate with your trackers. It is impossible to search for leads using them, they are not displayed in statistics reports, but they can be used for the technical side of integration - in API or postbacks.
subid
,uuid
,sub1
,sub2
,sub3
,sub4
,sub5
- custom tag up to 255 characters, perfect for any kind of trackers.fbclid
,gclid
,adclid
,ttclid
,unique_id
- automatic tag, which retrieves the click ID of ad networks.
The postback uses macros of the same name in curly braces, for example {subid}
, {uuid}
, {fbclid}
and so on.
Arbitrary code on sites
Some offers allow you to install arbitrary code on websites that you can use for custom tracking systems. The code for the site header is indicated at the end of the head
tag, the code for the footer is indicated at the end of the body
. The same code is installed on all pages of the site, including the "Thank you" page.
You can use macros that match the parameters from the request: {utm_source}
, {utm_campaign}
, {utm_content}
, {utm_term}
, {utm_medium}
, {subid}
, {uuid}
, {uid}
, {fb}
, {fbe}
, {ga}
, {gad}
, {mt}
, {mtrk}
, {tt}
, {lki}
.
Arbitrary code in iframe
Some external offers support setting their own iframes, in which you can specify any arbitrary code. Depending on the offer, there may be a single iframe for all pages or a different code for the site and the "Thank you" page.
You can use macros that match the parameters from the request: {utm_source}
, {utm_campaign}
, {utm_content}
, {utm_term}
, {utm_medium}
, {subid}
, {uuid}
, {uid}
, {fb}
, {fbe}
, {ga}
, {gad}
, {mt}
, {mtrk}
, {tt}
, {lki}
.