Date: May 29, 2025
Context:
To comply with Chrome's Protected Audience requirements, the project needed to serve an attestation file at a well-known endpoint.
Decision:
An attestation file (attestation.json) was added and served via the route /well-known/attestation/attestation.json. This file contains metadata required for Chrome's Protected Audience.
Consequences:
This enables the project to integrate with Chrome's Protected Audience, ensuring compliance and compatibility with modern browser standards.
Date: May 29, 2025
Context:
The project required integration with Taboola's server-to-server (S2S) API to track purchase events and enhance ad targeting.
Decision:
A new feature was added to send purchase events to Taboola's S2S API. This included handling UTM parameters and ensuring data consistency.
Consequences:
This integration improves ad targeting and tracking capabilities, providing better insights into user behavior.
Date: May 29, 2025
Context:
To enhance user data mapping, the project needed to integrate with Truecaller to fetch UTM parameters and validate user data.
Decision:
Truecaller integration was implemented, allowing the system to fetch UTM parameters and validate user data against Truecaller's database.
Consequences:
This integration improves the accuracy of user data mapping and enhances the system's ability to track user activity.
Date: May 29, 2025
Context:
To ensure secure integration with WebEngage, the project needed to implement domain whitelisting.
Decision:
A check for whitelisted domains was added to the WebEngage integration, ensuring that only trusted domains can interact with the system.
Consequences:
This improves the security of the WebEngage integration and prevents unauthorized access.