Tracking URLs
A tracking URL specifies where to send data when users view or click your ads as well as what data you want to receive.
Using tracking URLs
Here is a typical workflow for using tracking URLs in justtrack:
- When you connect a partner to your organization in justtrack, you usually need to configure two tracking URLs. The first is for when a user sees your ad. (This is called an impression.) The second is for when a user clicks your ad. At this stage, the tracking URLs are more like templates that specify what information you want to receive and the way you want to receive it; but more on that later.
- When you create a campaign in the partner, you:
- Build a tracking URL that's specific to an app, platform, and goal*.
- Add this tracking URL to the partner campaign.
- When the partner places the ad, it includes these tracker URLs.
- When the user sees or clicks the ad, the partner SDK sends tracking data to the correct URL where you can see the results in real time.
*Goals aren't always required when building tracking URLs. They're only required if the partner you're connecting supports both:
- Automatic campaign creation
- Sending cost data via tracking URLs
The data you receive from tracking URLs is valuable for things like understanding how effective your campaign is at achieving some goal or attributing user behaviours to the partners that run the campaigns.
Some partners don't support external tracking URLs. In those cases, we can't show impression or click data.
Tracking URL components
A tracking URL is composed of three parts:
Domain
The domain is the address that receives data about the partner, the campaign, and user who sees or clicks your ad.
Event
The event identifies the interaction the user had with your advertisement. The two possible values are:
viewclick
Parameters
The parameters specify the data you want to receive for your campaign. This data might include the user's country, the campaign type, or the goal you're basing your campaign on.
There are two types of parameters:
- Those that justtrack provides values for.
- Those that the partner provides values for.
justtrack parameters
Some parameters are managed by justtrack. When you build a URL for a campaign, justtrack provides these values in the tracking URL:
| Parameter Name | Description |
|---|---|
goalName | Unique name of the default or custom goal |
network | The justtrack ID for the connected partner |
storeId | Store ID for Apple iTunes/App Store app, or the package name for Google Play |
Partner parameters
Some parameters are managed by the partner. When a user interacts with the ad, the partner provides values for these parameters:
| Parameter Name | Description | Included by default |
|---|---|---|
deviceId | Google Advertiser ID / Identifier for Advertisers |  |
clickId | Partner generated unique ID of the click (click links only) | |
viewId | Partner generated unique ID of the view (view links only) | |
sourceId | Sub ID | |
sourceBundleId | Sub App ID | |
sourceCampaignId | Campaign ID of the partner | |
creativeName | Name of the set of creative assets (provided by AppLike). | |
sourcePublisher | App publisher | |
creativeId | ID of the set of creative assets (provided by AppLike) | |
referrerId | Partner generated unique ID of the referrer (click links only) | |
sourceUrl | App store URL in which the ad was shown | |
sourcePlacement | Placement within the publisher’s app | |
sourceCategory | Category of the publisher’s app in which the ad was shown | |
channel | Ad unit | |
adType | Type of shown creative asset | |
limitedAdTracking | "1" or "true" if ad tracking is limited, "0" or "false" if ad tracking isn't limited | |
country | GEO country of the user (ISO3166 alpha-2) | |
osVersion | Operating system version | |
deviceType | Device type (tablet, phone, etc.) | |
deviceModel | Device model | |
deviceResolution | User device’s screen resolution | |
s2s | true/false: Describes if the click/view was executed by the server or by frontend | |
exchangeId | ID of ad exchange | |
exchangeName | Name of ad exchange | |
sourceName | Name of the publisher’s app in which the ad was shown | |
deviceVendor | Should be "apple" for iOS platform or empty | |
adSetId | Ad set/group ID of the partner | |
bidType | Campaign cost model ("CPI", "CPA", "CPC", "CPM", "CPV", "CPCV") |  |
bidCurrency | CPI/CPA currency. This is required for cost tracking via clicks and views. | |
bidValue | CPI/CPA value (use . as decimal delimiter). This is required for cost tracking via clicks and views. | |
userAgent | User agent of the tracking event | |
ip | Current GEO IP of the tracking event | |
redirect | Prevents user getting redirected to the Play store if set to false | |
custom0 | Optional custom parameter | |
custom1 | Optional custom parameter | |
custom2 | Optional custom parameter | |
custom3 | Optional custom parameter | |
campaignType | "retargeting" for retargeting campaigns, "acquisition" for acquisition campaigns | |
optimizationType | The optimization type of the campaign | |
sourceCampaignName | Name of the campaign in partner | |
adSetName | Name of the ad set, ad group, offer | |
Macros
When you connect a partner to justtrack, you create templates for your tracking URLs. These templates use macros for the parameters so the values can be added later:
By the time the user interacts with the ad, all these macros are replaced by real values.
You can include fixed values instead of macros if you don't want to receive dynamic tracking data from your partner.
For justtrack parameters, the macros you provide are arbitrary. For partner parameters, the macros you provide are specific to the partner. Please consult the partner's documentation to learn what macros you should use to get the correct data in your tracking URL.
If you use macros that aren't approved by the ad partner, we won't receive real data in the tracking URL.