Overview
If your publisher doesn't have a dedicated integration article, this guide shows you how to set up PEA Chain attribution for any generic publisher.
Since click IDs can no longer be reliably transmitted under iOS 14.5+, your publisher needs another way to identify their traffic source. Swaarm offers two methods for this.
ℹ️ For more on how PEA Chain works → Privacy Enabled Attribution
Method 1 - PEA Chain Parameter
The free-form click parameter pea_chain can be used to pass any information needed to identify the traffic source. The format is left to the publisher - they can choose whatever works for them, and Swaarm will pass it back in the postback.
A few things to keep in mind when choosing the format:
Cardinality of values - limit the number of unique values sent in this parameter for a given offer
Length of the parameter value - keep the total length as minimal as possible. While Swaarm doesn't impose a strict limit, some MMPs or advertisers might - in that case Swaarm will truncate the value to help ensure attribution still succeeds.
Publisher Click parameter: pea_chain
Publisher Postback macro: #{peaChain}
Method 2 - Separate Offer and Publisher IDs
If your publisher can only transmit their offer ID and publisher ID as separate fields, use the following click parameters instead:
ext_offer_id- the offer ID in the publisher's own platformext_publisher_id- the publisher ID in the publisher's own platform
Corresponding postback macros: #{ext.offerId} and #{ext.publisherId} respectively.