Roku Sync

Overview of Project Discussion

  • The discussion centers around using the Roku ad ID (RIDA) for tracking and targeting in partnership with Cochaba.

Key Components of the Project

  • Roku Ad ID (RIDA):

    • Used through the client API for Cochaba tracking.

    • Serves as a match key identifier for targeting purposes.

  • Targeting Segments:

    • Data collected will be segmented into various targets (labeled as segment one, segment two, etc.).

    • The intent is to include customers who engage heavily with Prime Video and exclude less active users.

Privacy and Data Compliance

  • Obfuscation Requirement:

    • Data lists must be obfuscated to ensure user privacy; identifiable customer information cannot be shared.

    • Labels will only indicate segment numbers without revealing customer identities.

  • Daily Audience Refresh:

    • Audiences must be refreshed daily to respect customer opt-outs.

    • This request must be fulfilled by the partner in order to ensure compliance.

Questions and Clarifications

  • Wait for Structure:

    • Further inquiries about how audience targeting could be both inclusively and exclusively done.

    • Heavy engagers versus less frequent users of Prime Video will be the primary targets.

  • Integration with Other Targeting Techniques:

    • Emphasis on collaboration between the teams, leveraging both Amazon's and Roku's data.

    • Anticipation for a deeper integration or collaboration in future campaigns.

Next Steps and Deliverables

  • Delivery Methods:

    • Discussion on preferred folder structures and documentation of delivery methods is needed.

  • Legal Agreement:

    • There is a necessary marketing data sharing agreement for the project.

    • Generally accepted language typical for media buying agreements.

    • Important for partners to remember that they cannot repurpose the data for other means.

  • Legal Timing and Procedures:

    • The process of getting the contract from legal teams takes time (approximately a month).

    • Communication and collaboration between legal teams can expedite the process.

Technical Infrastructure

  • S3 Pathway Discussion:

    • Current infrastructure includes an existing Amazon S3 bucket set up with prior cooperation.

    • Potentially using the same accounts but requires legal clarification on data implications specific to this project.

  • Global Scaling:

    • Opportunity to extend the project beyond the U.S., including Canada and Latin America, as opportunities arise.

Collaboration and Communication

  • Regular Updates:

    • Ongoing communication is encouraged to clarify any uncertainties while preparing documentation.

    • Legal teams being accessible for direct discussions regarding any contract languages or questions.

  • Planning for Future Collaboration:

    • Emphasis on ensuring that the setup is scalable to other active territories without repeating the contract-signing process.

Concluding Remarks

  • The dialogue concluded without additional questions, affirming a positive outlook towards moving forward with the project and coordinated efforts among teams.