- Reset your user data and/or opt out
-
- DFP key/val pairs will be in format "s=20;s=198;"
-
- Interfaces for test harness:
-
- View mediabrix cookies & data
- View Exelate segments
- View expiration date on DMP data
- View the generated ad tag
- Expire DMP data
- Regression testing on monday
- Set up a fake advertiser beacon page with key/val for retargeting.
-
- Input fields for key/val
- Input field so you can change your Mediabrix GUID
- TO DO:
-
- Setup test campaigns with different creatives
- Cookies:
-
- mb_unique - mediabrix unique ID
- mb_dmp - dmp data
- mb_expiry - expiration date for dmp data
- mb_optout - opt out cookie
<script src="
https://mediabrix.hs.llnwd.net/o38/targeting/dmp_optout.js" type="text/javascript"></script>
Here is the sandbox tag you requested:
https://load.exelator.com/load/?p=104&g=580&j=jf
You can QA w/ the following methods:
Please let us know how QA pans out, and also -- please provide the opt-out URL at your earliest convenience.
Thanks,
CV
- Opt -0ut
-
- Send JSON structure of the user to Exelate
- Flag mediabrix cookie "opt-out"
- support client side and server-to-server opt outs
- Q: How will Exelate identify the user to the MediaBrix Opt Out service?
- Q: How are opted out users identified by Exelate's API? Likely with a "service:off" flag but need confirmation.
-
- Service:off is for our RTD account
- Q: Is the Exelate cookie a browser cookie or flash cookie?
- DFP keywords:
-
- How does DFP handle targeting? is it an and/or situation?
- JSON Structure and taxonomy handling
-
- Ignore age and gender. Data will be the segment IDs available
- Next steps:
-
- Architect opt out service (Lee & Tejas)
- Sandbox setup(Exelate)
- Client-side integration (Lee)
- DFP keyword targeting research (Lee)
Implementation Notes
- Integration of DMP's API in the web client (Lee/Tejas/JaimeM?)
-
- Exelate API integrated with MediaBrix's ad call script via JavaScript callbacks
-
- JSON format: {“service” : “on”,“age” : 28,“gender” : “female”, “segments” : [234,235,269]}
- API called only if there is no MediaBrix unique cookie or if the cookie's user data has expired
- Applicable to all SocialFlex and SocialViews versions
- Not applicable to iframe deployments
- Web client appends key/val pairs to the ad tag
- Key/val pairs added to the apptrak data
- User data stored in database and MediaBrix unique cookie
- MediaBrix Unique Cookie values(Lee)
-
- MB unique ID
- All user data from Exelate
- Expires in 7 days
- Flagged with "opted out" if the user has opted out through Exelate's web site.
-
- Q: How are opted out users identified by Exelate's API? Likely with a "service:off" flag but need confirmation.
- Matching DMP segments with MediaBrix key/val definitions(Jay/Stephen/Sandro/Lee)
-
- Requires a predefined list of targets
- Targets must correspond to the taxonomy available from Exelate.
- Targets used in DFP must be published to MediaBrix's ad call script.
- Opt Out Service(Tejas)
-
- User opts out via Exelate.com
- Exelate pings our web service to delete the user's information from our DB
-
- Q: How will Exelate identify the user to the MediaBrix Opt Out service?
- MediaBrix logs an opt-out apptrak event
Exelate meeting notes - 09/27
- Account setup by next week
-
- Unique URL for our calls
- Updated segment values documentation
- What do we need to provide to Exelate?
-
- Call the service one time per unique user per day
- 10,000,000 max calls per day
- Sample of JSON data format we want
- Global opt out
-
- User opt outs via Exelate
- Exelate responds that the user has opted out
- MB records that the user has opted out and we do not call the service for that user
- Web client drops an opt-out cookie on the user's browser
- Questions:
-
- Performance of round trip from Publisher > DMP > Platform
- If key/val are appended but not targeted in DFP, will it serve a non-targeted ad?
- What versions will we
- Data available
-
- Demographic
- Intent
- Interest
Buyer Opt-Out Requirements.pdfeXelate_RTD_Overview.pdf