VDM Next — Audience Integration (rudder-transformer)

Objective: Build the transformation logic for a new VDM Next audience destination — process warehouse record events into HTTP API requests that add/remove users from audience segments, with identifier normalization, hashing, and batching.

Context

This is the transformer step in building a VDM Next audience integration.

Audience destinations share these traits:

• Operations are add (insert/update) and remove (delete) on audience membership
• Records contain identifiers (email, phone, ad IDs) that may require normalization and hashing
• Batching is by user count (destination API limits) and optionally payload size
• Some destinations support multiple audience subtypes (user vs company, standard vs value-based)

File Structure