Transitioning Client-Side Vendor Tags to Event Forwarding Properties

Introduction

Transitioning client-side vendor tags to server-side event forwarding properties offers several advantages, especially in light of evolving browser policies and data privacy concerns. This document outlines the evaluation process for migrating client-side vendor tags to event forwarding properties within Adobe Experience Platform.

Understanding the Evaluation Process

Before migrating a client-side vendor tag, it’s essential to assess its use cases, data requirements, and API compatibility for server-to-server data transfer. This evaluation ensures a seamless transition without compromising data integrity or functionality.

Assessing Use Cases and Data Requirements

1. Use Cases Identification:
   • Define specific use cases currently implemented with the client-side vendor tag. For example, consider scenarios where data from the Facebook (Meta) pixel is used to track conversions after interactions with ads.
2. Data Points and Transfer:
   • Document which events and data points are captured and passed to the client-side tag. Identify when and where data transfers occur during visitor interactions on the site.
3. Data Mapping:
   • Create a comprehensive record (e.g., list, spreadsheet, diagram) detailing data sources, destinations, and transformations. Include considerations for capturing required data without the client-side tag.

Vendor API Investigation

1. API Capability Assessment:
   • Determine if the vendor provides APIs designed for server-to-server transfer of event data. Investigate the following:
     • Existence of API Endpoints: Check if the vendor’s API supports endpoints required for your specific use cases.
     • Data Transfer Methods: Verify if the API supports streaming or batch data transfers.
     • Authentication Requirements: Identify supported authentication methods (e.g., token, OAuth client credentials) compatible with event forwarding.
2. Data Requirements:
   • Confirm the data fields required by the vendor for relevant API endpoints. Determine if a vendor-specific user identifier is mandatory for each API call.

Feasibility for Event Forwarding

1. Compatibility Check:
   • Ensure that the vendor’s API endpoints, authentication methods, and data requirements align with the needs of your use cases.
2. Data Accessibility:
   • Evaluate if all necessary data can be accessed either directly from the client-side or through alternative API calls, without relying on the client-side vendor tag.

Conclusion

Migrating client-side vendor tags to event forwarding properties can enhance data security and compliance while optimizing performance. By carefully evaluating use cases, data requirements, and vendor API capabilities, organizations can make informed decisions to transition tags effectively.