Activity

1. aram356

   added the

   Task

   issue type on Nov 10, 2025
2. aram356

   added a parent issue on Nov 10, 2025

   • Integrate Permutive Support for Publishers #57
3. aram356

   assigned

   ChristianPavilonis

   on Nov 10, 2025
4. ChristianPavilonis commented on Nov 18, 2025

   

   ChristianPavilonis

   on Nov 18, 2025

   Last edited by ChristianPavilonis

   Collaborator

   More actions

   Permutive call stack analysis

   (Analysis generated from HAR file prospecta-permutive.har)

   Overview

   This HAR trace includes several network requests to Permutive, a data management and analytics platform used for audience segmentation, consent management, and advertising personalization. The trace shows that prospecta site integrates Permutive both as a CDN-loaded JavaScript library and through backend API endpoints for event tracking and user synchronization.

   Step-by-step breakdown

   1. Script loading

   • URL example: https://cdn.permutive.com/prospecta/xyz123-web.js
   • Purpose: The browser first downloads a JavaScript SDK from the Permutive CDN. This script initializes the Permutive runtime within the page, sets up event listeners, and reads any stored identifiers or consent tokens from local storage or cookies.
   • What happens next: Once loaded, the script queues initial events (page view, user session) and loads configuration from Permutive’s project settings.

   2. Initialization call

   • URL example: https://api.permutive.com/v2/projects/abc123/config
   • Purpose: Fetches configuration for the prospecta project. This includes project ID, enabled modules (segmentation, identity sync, publisher integrations), and sampling rules.
   • Data sent: Usually minimal—mostly the site’s project key, environment, and SDK version.
   • Data received: A JSON configuration that defines which segments, events, and partner pixels should be active.

   3. Event collection

   • URL example: https://events.permutive.app/collect
   • Purpose: Sends event payloads such as pageView, contentView, or custom behavioral events triggered by the SDK.
   • Data sent: Contains anonymous or pseudonymous identifiers (UUIDs or hashed IDs), timestamps, event names, and contextual metadata (page category, article ID, user device type, etc.).
   • Response: Usually a 204 No Content—server simply acknowledges receipt.

   4. Identity synchronization

   • URL example: https://sync.permutive.com/v1/sync
   • Purpose: Syncs user IDs with external partners (e.g., The Trade Desk, Google, or other SSP/DSPs). This allows ad systems to align audience segments.
   • Data sent: Includes a unique Permutive user ID and partner IDs if already known. Sometimes cookies like _puid or _permutive-id are referenced.
   • Response: Often returns JSON mapping or triggers redirects to partner sync URLs.

   5. Segment updates

   • URL example: https://api.permutive.com/v1/segments
   • Purpose: Requests or updates which audience segments the current user belongs to based on prior behavior.
   • Data sent: Permutive user ID, project ID, and event triggers.
   • Response: A JSON array of active segment identifiers.

   Overall flow summary

   1. CDN script loads and boots the SDK.
   2. Configuration fetched to understand which events and integrations to run.
   3. Events collected and sent to the /collect endpoint.
   4. Segments synced and updated locally.
   5. Partner syncs propagate IDs to external ad networks.

   Components involved

   Component	Role	Notes
   cdn.permutive.com	Hosts JavaScript SDK	Static script defining client logic
   api.permutive.com	Configuration & segment updates	Used during initialization and segmentation
   events.permutive.app	Event collection endpoint	Receives behavioral events
   sync.permutive.com	Identity synchronization	Connects to partner ad systems
   Local Storage & Cookies	Client persistence	Keeps user/session data between visits

   Initiator data

   Looks like all the permutive calls that I've seen are from first party scripts, or they're just in the nextjs/webpack chunks.
5. aram356

   added a sub-issue on Nov 20, 2025

   • Ask for test account for Permutive #122
6. aram356

   removed a sub-issue on Nov 20, 2025

   • Ask for test account for Permutive #122
7. aram356

   closed this as completedon Dec 8, 2025
8. aram356 commented on Dec 15, 2025

   

   aram356

   on Dec 15, 2025

   CollaboratorAuthor

   More actions

   🔧 Can you please recover linked document?