0%

Postbacking conversion information to mediasmart

Overview

Posting back conversion information to us via S2S allows us to track performance accurately and optimize campaigns in real time. It ensures better attribution and faster algorithm learning for improved results.

You will be able to download the S2S postbacks to add on your server directly from your campaign Properties section.

Keep reading for more information about correct setup.

Process

  1. Download the S2S postbacks directly from our platform within the specific campaign you want to track.

  2. You (or your client) will set up one or more postbacks on your server to send us the user conversion data you're tracking.

  3. Our system will then process this information and use it to optimize campaign performance in real time. This includes populating audiences to block or find lookalikes.

Correct Postback format

The postback you will download follows this format:

https://3ma79ae7cua.com/m/open?id={ADVERTISER_ID}&msxt={ms_user_id}&ms_ip={IP_VALUE}&ms_ua={USER_AGENT_VALUE}&ms_event_num=1

Where:

  • {ADVERTISER_ID} should be replaced with the actual advertiser ID of the campaign. It should look like this: advertiser-jiedxntoawailuf0xa1vmjkqldbb2m04

  • {ms_user_id} should be dynamically replaced by the %msxt% value that we’ll send with the impression and click tracker.

  • The event number coming after ms_event_num= can be any number between 1 and 5. This event number can later be used as an optimization goal.

  • (Optional) The ms_ip={IP_VALUE}, and ms_ua={USER_AGENT_VALUE} parameters are optional.

  • (Optional) You can add additional parameters if you'd like to receive more information.

This step will mean we automatically send you the user information that you'll need to post back once the conversion is measured on your side.

Considerations

  • Test before going live. Run an end-to-end test to ensure the tracking is properly working.

  • Event deduplication: Make sure to send one postback per event (i.e. event1=install, event2=purchase). Use event numbers to distinguish multiple events per user.

    • If you are running a Drive-to-store campaign and want to pass additional information through S2S, do not use Conversion 1 or Event 1; as it is where we add attributed visits.

  • Send conversion data as soon as the event happens to support real-time optimization.

  • Make sure to collect user consent when operating in countries with privacy regulations.

  • Secure your endpoint: Ensure your server receiving or sending postbacks is stable, secure, and handles retries if needed.

0%