In this article, we are going to explain how the Tracking URL and the Postback URL template should look like for Appmetrica/Yandex.
It is important to note these are suggested templates that you can use, but you can add or delete some parameters and macros based on your company's requirements.
Appmetrica/Yandex Tracking URL template:
Appmetrica/Yandex tracking link contains the minimum information to record the click and redirect the user to download the app. Additional parameters must be added to the link after the “?” character, to record extra information and get back the information via the postback link. This is how the base tracking URL looks like,
Structure:
https://redirect.appmetrica.yandex.com/serve/[tracking ID — The ID of the tracker]
Example:
https://redirect.appmetrica.yandex.com/serve/1019409635088005254?click_id={id}&google_aid={device.ids.gaid}redirect.appmetrica.yandex.com — is the predominantly used domain. However, some possible variations are:
appmetrika.yandex.com
appmetrica.yandex.ru
appmetrika.yandex.ru
The base tracking URL link includes the tracking ID and shared below is the expected format of the complete tracking URL once the additional Swaarm macros have been incorporated:
https://redirect.appmetrica.yandex.com/serve/600573419754384676?click_id={id}&google_aid={device.ids.gaid}&ios_ifa={device.ids.idfa}&device_ip={user.ip}&device_ua={user.encoded_ua}&click_timestamp={time.timestamp}&afpub_id={publisher.id}_{publisher.subId}&site_id={publisher.site}&creative_id={publisher.creative}
Additional Tracking Link mapping:
Appmetrica Parameters | Appmetrica Parameters Description | Swaarm Macros | Swaarm Macros Description |
click_id | Macro for transmitting a unique click ID | {id} | Swaarm click ID(mandatory pass) |
google_aid | Google AID | {device.ids.gaid} | Google advertising identifier |
google_aid_sha1 | SHA1 hash of Google AID | {device.ids.gaid.sha1} | sha1 of Google advertising identifier |
ios_ifa | IFA | {device.ids.idfa} | Apple iOS advertising identifier |
ios_ifa_sha1 | SHA1 hash of IFA | {device.ids.idfa.sha1} | Sha1 of Apple iOS advertising identifier |
device_ip | The device's URL-encoded IP address | {user.ip} | IP of the user device |
device_ua | The device's URL-encoded User-Agent | {user.encoded_ua} | URL-encoded user agent string determined at the time of click |
click_timestamp | UTC timestamp of the click in seconds | {time.timestamp} | returns the event’s UNIX timestamp |
afpub_id | ID of an affiliated publisher (sub-partner) | {publisher.id}_{publisher.subId} | Swaarm network Publisher ID & |
site_id | ID of a specific advertising place | {publisher.site} | Publisher site identifier |
creative_id | ID of a specific banner | {publisher.creative} | Publisher creative ID/name |
For the full list of Macros supported by Swaarm, here
You can find the additional tracking link parameters supported by Appmetrica/Yandex,
here.
Appmetrica/Yandex Postback URL template:
This is how the global postback should look like after adding the Appmetrica/Yandex -supported macros,
https://track.yournetwork.swaarm-clients.com/postback?click_id={click_id}&event_id={conversion_event_name}&gaid={google_aid}&idfa={ios_ifa}&sale_amount={price}
Additional Postback Link mapping:
Swaarm Parameters | Swaarm Parameters Description | Appmertica Macros | Appmertica Macros Description |
click_id | Swaarm click id for the user for which the conversion is attributed | {click_id} | The unique click ID |
match_type | Attribution method (fingerprint; device_tag; reftag; external_click_id; google; facebook) | {match_type} | How the click was associated with the installation. Possible values: referrer | fingerprint | identifier |
postback_id | Postback ID passed by the Advertiser | {transaction_id} | ID of this occurrence of the event or installation. For example, if the same device generates the same event, transaction_id changes |
user_agent | User Device UserAgent | {click_user_agent} | User-agent of the click |
click_timestamp | Click timestamp recorded by the advertiser’s SDK on click | {click_datetime} | UTC date and time of the click in RFC3339 format. |
conversion_timestamp | Conversion timestamp recorded by the advertiser’s SDK on conversion | {conversion_timestamp} | Time of conversion (event on the device) in Unix timestamp format, in seconds |
event_id | Id of the event attributed in the advertiser’s SDK | {conversion_event_name} | Name of the event for registering the conversion |
event_value | JSON object containing all the custom event information collected by the SDK | {conversion_event_json} | Nested event attributes in JSON format |
installed_at | Time recorded by the SDK when the app was opened for the first time | {install_datetime} | UTC date and time of installation in RFC3339 format |
install_finish_time | App download completion timestamp | {install_timestamp} | Time of installation in Unix timestamp format, in seconds |
gaid | Google Aid of the device | {google_aid} | The device's Google AID in the format it was received from the device in |
idfa | IDFA of the iOS device | {ios_ifa} | The device's IFA in the format it was received from the device in |
device_manufacturer | Device manufacturer name of the device that installed the app | {device_manufacturer} | The device manufacturer detected by the AppMetrica service (for example, Apple or Samsung) |
device_name | Device model number of the device that installed the app | {device_model} | The device model detected by the AppMetrica service (for example, Galaxy S6). |
device_language | User Device Language | {device_locale} | The language on the device |
os_name | Operating system of the device that installed the app | {os_name} | Operating system. Possible values: ios | android | windows |
os_version | Operating system version number of the device that installed the app | {os_version} | The version of the operating system on the user's device |
isp | Internet service provider of the device that installed the app | {operator_name} | The name of the mobile operator |
app_version | Version of the App | {app_version_name} | The app version in the format specified by the developer |
app_title | App title/name of publisher app | {app_package_name} | The package name for Android or the Bundle ID for iOS (for example, ru.yandex.metro) |
sdk_version | The version of the SDK used by the advertiser | {appmetrica_sdk_version} | The AppMetrica SDK version that has been integrated into the application |
app_id | App ID of the Publisher App | {store_app_id} | Application ID in Google Play or App Store |
sale_amount | The revenue per conversion we made in the advertiser platform | {price} | The purchase or product cost |
sale_amount_currency | Currency of the revenue per conversion we made in the advertiser platform | {currency} | The purchase currency |
Note:
The domain name (
yournetwork) should be replaced with your own postback domain.The event will be tracked based on Appmetrica's event name, so it should be placed on the Swaarm event page in Adv.EventType ID section as follows,
For the full list of Postback parameters supported by Swaarm, here
You can find the additional Postback link macros supported by Appmetrica/Yandex, here