Affise MMP is a mobile measurement partner offering a brand new and quality service and expanding the list of media source integrations to cater for any type of user with different needs in integrations.
Here is a set of points/FAQs for a media source integration:
1. Make use of official integration documentation for Affise MMP:
Affise MMP Help Center with a detailed description of UI and tracking - https://intercom.help/affise-mmp/en
SDK IOS Documentation - https://github.com/affise/sdk-ios
SDK Android Documentation - https://github.com/affise/sdk-android
Other SDK - https://github.com/affise
2. How does the communication happen?
Affise MMP team uses all communication channels for the customers regarding the operation of the service and for all integration partners. Communication is supported via a Skype chat, Telegram chat, WhatsApp chat or Slack channel, etc. The response time to the request is 15 - 30 minutes after the request in European time. If an issue arises at non-working time, a support manager assists in resolving issues.
🔎 Email for communication: [email protected]
3. Adding official integration documentation.
Affise MMP team is to publish integration materials in the integration section for all the points that you have indicated.
Please send an example of documentation, and Affise MMP team will be able to tell you in detail how it will look in the instructions and in the system. Also, you will be placed as an integrated partner inside the system in the integrated partners section, and in the list on the company and product website.
4. Tracking and postbacks.
Affise MMP system supports 4 types of postbacks for all channels. All postbacks are sent in real time when an action or event is performed.
⚠️ The exception may be iOS postbacks received from the SKAd Network, which will be sent after Affise MMP system receives them from Apple.
The supported postbacks are the following:
Cross postback: a postback for sending data to any client systems, Bi systems, analytics systems, or advertising platform systems. https://help-center.affisemmp.com/en/articles/9772453-applications#h_32411f0ec3
Default postback: a postback to send an install to the default system, for example, a performance tracker, or an advertising platform. https://help-center.affisemmp.com/en/articles/9814851-postback-url-setup#h_febd8bcaf3
Partner postback: a postback to send to a partner, publisher, traffic source. https://help-center.affisemmp.com/en/articles/9775600-add-a-partner#h_7695d807a8
Conversion type postback (Event Postback): a postback for sending a specific action: installation, registration, purchase, subscription, order, start trial, custom event, etc. https://help-center.affisemmp.com/en/articles/9814851-postback-url-setup#h_4bd598d0e9
5. Anti-Froud tools.
Affise MMP offers basic functionality that tracks fraud when the system is running, monitors VPNs, proxies, device farms (Amazon, Google, etc.), root devices, and device emulators. Such installations are not counted as non-organic, but are considered as organic.
Affise MMP does not limit customers to using some kind of fraud protection solution but offers them integration with different systems, for example, 24 metrics, and Fraudscore.
🔎 If necessary, the customers can use a macro for postback to send a message that this installation has a sign of fraud.
6. Attribution: Clicks, Impressions, Device ID.
Affise MMP system supports attribution by click and by impression. Here is the example of links:
Click: https://trk.affattr.com/2SQ957QIUPGF0?clickid={clickid}&pid=675
Impression: https://trk.affattr.com/imp/2SQ957QIUPGF0
The system also supports device ID attribution and probabilistic attribution.
Documentation: https://affise.notion.site/Pub-Model-Affise-Attribution-Eng-6077cce8f1474442bc09c1d21938114e?pvs=4
7. Support customer-adjusted impressions and click device id or probabilistic attribution windows.
The customers can configure the attribution windows for the Fingerprint DeviceID and Google Referrer parameters themselves.
For Fingerprint: from 1 hour to 7 Days (Default 24 hours (1 Day)).
For DeviceID and Google Referrer: from 1 hour to 30 Days (Default 24 hours (1 Day)).
View-through: 1 - 7 Days (Default 1 day)
Click-through: 1 - 30 Days (Default 7 days)
8. In cases where there is a device ID, but attribution is not possible, will probabilistic attribution be used as a solution?
Yes, probabilistic attribution is used. Also, it's possible to use it for Android devices (this setting can be enabled by the customer if necessary), the system is already ready to work with Google SandBox.
9. Support server-side reporting of clicks or impressions. S2S reports and tracking.
Affise MMP supports S2S attribution and reporting events, the parameters are the same as for tracking links. If possible, it is also necessary to transfer the User Agent parameters, and the data about devices (model, manufacturer, OS, OS version, firmware version).
Parameters: https://help-center.affisemmp.com/en/articles/9799723-tracking-and-postback-urls-parameters-and-macros
Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].