Integration change requests for integrated partners

At a glance: Enable quick turnaround of your integration changes by providing the necessary information with the initial request.

 Important!

ZendeskConnect postbacks and attribution URL structures are global. This means that any change of these structures impacts all existing and future campaigns across all apps.

Request	Details	Requirements
Enable view-through attribution	Allow view-through attribution measurement. The macro attributed_touch_type contains impression or click to indicate the engagement type.  More on view-through attribution.	Send an email to [e-mail] with the subject Enable VTA. Include: Your PID or Partner Dashboard login [Recommended] Your receiving parameter name associated with the macro
Enable rejected installs and in-app events postback	Get postbacks of rejected installs and in-app events due to fraud or non-compliance with validation rules. Include the macros listed in the postback to differentiate between rejected and legitimate installs/events and see the reason for the block: is-rejected blocked-reason blocked-sub-reason blocked-reason-value More on rejected installs and in-app event postbacks.	Send an email to [e-mail] with the subject Rejected install/in-app postback. Include:  Your PID or Partner Dashboard login [Recommended] For each macro listed provide a receiving parameter name Indicate if rejected in-app events together with rejected installs are sent in the postback.
Enable retargeting	Allow retargeting activity measurement. ZendeskConnect provides the following macros in the postback to identify if the campaign is a retargeting campaign and the conversion type (re-attribution or re-engagement): is-retarget retargeting_conversion_type More about retargeting.	Send an email to [e-mail] with the subject Enable Retargeting. Include: Your PID or Partner Dashboard login [Recommended] The names of the receiving parameters (defined by your technical team) for the macros is-retarget and retargeting_conversion_type, if you want to receive these values via your existing integrated regular install/in-app event postback. Which type of postback (install postback/in-app event postback/both of them) these parameters must be added to Indicate if a re-engagement postback is required for re-engagement events (meaning the first  app-open of an existing app after clicking on a retargeting campaign ad)
Enable uninstall	Get postbacks of af_uninstall in-app events to measure uninstalls. More on uninstalls.	Send an email to [e-mail] with the subject Enable af_uninstall in-app event postback. Include: Your PID or Partner Dashboard login
Add additional postback endpoint	Additional postback endpoint to gradually migrate from one performance marketing platform to another or work with several performance marketing platforms. Define the endpoint that ZendeskConnect uses if an advertiser adds af_additionalpostback=1 to the attribution link.  Postbacks aren't sent in parallel to both endpoints but only to one endpoint. The current postback template is used as the fallback endpoint unless specified otherwise.	Send an email to [e-mail] with the subject Add additional postback endpoint. Include: Your PID or Partner Dashboard login The new endpoint to use for af_additionalpostback=1 (both for installs and in-app events)
Enable sending session data	Allow data sharing for af_app_opened in-app event. More about session data.	Send an email to [e-mail] with the subject Enable af_app_opened postback. Include: Your PID or Partner Dashboard login
Enable postbacks retry	Enable sending a postback several times in case of a sending failure. Use postback-id macro to identify the postback ID. More about postback retries.	Send an email to [e-mail] with the subject Enable Postbacks Retry. Include: Your PID The receiving parameter name for the postback-id macro
Update postback	Change the current postback structure (for example, delete/add parameters, change endpoint URL.) More about postbacks and macros.	Send an email to [e-mail] with the subject Update postback. Include: Your PID The new postback structure based on available macros.
Enable Advanced Privacy postback	Setup Advanced Privacy integration to comply with an advertiser's data sharing policy.  More about Advanced Privacy postbacks.	Follow the instructions for Advanced Privacy postback configuration in the ZendeskConnect dashboard. In case of any issues, send an email to [e-mail] with the subject Enable Advanced Privacy postback. Include: Your PID Advanced Privacy postback structure based on available macros
Enable SKAdNetwork postback	Setup SKAdNetwork integration and the ability to receive decoded data from ZendeskConnect via postbacks. More about SKAdNetwork postbacks.	Follow the instructions for SKAdNetwork postback configuration in the ZendeskConnect dashboard. In case of any issues, send an email to [e-mail] with the subject Enable SKAdNetwork postback. Include:  Your PID or Partner Dashboard login SKAdNetwork postback structure based on available macros from KB Apple SKAdNetwork ID
Update the logo	Add a logo, or replace the current one.	Send an email to [e-mail] with the subject Update the logo. Include: Your PID Your new logo (transparent PNG file, sized 200x50px)
Update the click attribution URL	Update click attribution URL that advertisers use for running campaigns with you. More about attribution links.	Send an email to [e-mail] with the subject Update click attribution URL. Include: Your PID, New parameters and their corresponding macros. Once the click attribution URL is updated: For existing and running campaigns, request from the advertiser to extract the updated click attribution URL for you For the new campaign, the click attribution URL is updated when the advertiser extracts it
Create/update the partner dashboard login email	Required to login to the ZendeskConnect account, checking dashboard data, and exporting reports from the ZendeskConnect dashboard.	Send an email to [e-mail] with the subject Update partner dashboard login. Include: Your PID New login email Once the dashboard login has been created/updated, use the new/updated email to reset the password
Disable integration	If integration is disabled, installs and in-app events aren't attributed to the disabled integration. Note: Before disabling, verify that advertisers have stopped working with the integration.	Send an email to [e-mail] with the subject Disable integration. Include: Your PID Which integration (install, in-app event) you want to disable
Add new dashboard parameter	Allow advertisers to provide a specific parameter in the ZendeskConnect advertiser dashboard, so they can be received via a postback.	Send an email to [e-mail] with the subject Add new dashboard parameter. Include: Your PID The new dashboard parameter name The receiving parameter—if you want to receive it via install or in-app event postback [Recommended] The description of the parameter that will be displayed in a tooltip next to the parameter field in the ZendeskConnect dashboard for advertisers
Provide the postback template to the partner	Review your current integration	Send an email to [e-mail] with the subject Provide postback template. Include: Your PID Specify which postback (install postback, in-app event postback, or rejected postback) you want to check
Implement click signing	Add signature validation to clicks to avoid fraud liabilities and so fraudulent clicks aren't attributed to your ad network.	Follow the instructions to implement click signing on your side. In case of questions, email [e-mail].