Working with destinations
Every destination Toplu delivers to falls into one of two groups, and it changes nothing about how you call the API.
ECAPI-native
Speaks the ECAPI standard directly. Your event reaches it close to as sent, no extra work per network. Google's Data Manager API is the confirmed example today, verified directly against Google's own field-mapping documentation.
Hand-built connector
Uses its own proprietary format instead of ECAPI. Toplu builds and maintains a dedicated connector for each of these, so the request you send stays identical, the mapping work happens on Toplu's side. See Schema mapping for what that actually involves.
You never choose which kind a destination is, you just list it in destinations. See Destinations for the current list and which category each one is in.
Need a hand?
Coding is hard sometimes, and that's okay. Visit our help center or reach out directly, we're here to help.