• Tracking Links
  
• • Set up by the mobile app or site, including up to 10 standard and custom parameters
  • ref_id parameter: unique transaction ID; in our case it would be the value_id from MB’s Value Exchange(VX) Service
  • Sample: http://hastrk2.com/serve?action=click&publisher_id=200&site_id=1000&ref_id=204ef7b0-f0c2-418a-d41f-177d12bcb263_5_PIC9lTBc-qLfXKpD2GJQNHDDhVD8IxHLCHQ-3O-cPDA-
  • Link Tracking Documentation: http://support.mobileapptracking.com/entries/22559923-Best-Practices-for-Tracking-Links
    
  • Unique Identifier Matching: http://support.mobileapptracking.com/entries/22592057-Methodologies-for-Attributing-Installs#uniqueidentifier
• Server-to-Server Postbacks 
  
• • Set up via template or manually within the HasOffers dashboard.
  • Posts directly to MediaBrix appending the ref_id value from the tracking link
  • Sample: http://rs.mediabrix.com/exchange/set?value_id=204ef7b0-f0c2-418a-d41f-177d12bcb263_5_PIC9lTBc-qLfXKpD2GJQNHDDhVD8IxHLCHQ-3O-cPDA-
  • Documentation: http://support.mobileapptracking.com/entries/22560357-How-to-Set-Up-Server-Postbacks
    
• MediaBrix Value Exchange
• • Transactions fulfilled via server-to-server postback
  • Polling is not an option for mobile. 
  • Change: VX fires the Acquisition event
  • Change: VX stores relevant Order information to correlate Acquisition event with other metrics
  • Change: VX does not expire value_id’s