Schema mapping
The actual work a connector does, not the transport, not the auth, the fields.
ECAPI-native: close to 1:1
Google's Data Manager API, verified directly against its own field-mapping guide, maps ECAPI's id to its own transaction_id, and converts ECAPI's Unix timestamp to RFC 3339. Small, mechanical conversions, not a redesign.
Hand-built: the fields genuinely don't line up
Amazon's Events API, verified field-by-field against its own docs, is the clearest example. It uses eventTime and conversionType instead of ECAPI's timestamp and event_type, makes its equivalent of data_set_id optional where ECAPI requires it, and needs several fields ECAPI doesn't define at all: countryCode, matchKeys, eventSource. Amazon co-authored the ECAPI spec and still built its own, separate schema, that gap is exactly why hand-built connectors exist as their own category of work.
Whichever category a destination falls into, your request to Toplu looks the same either way, see Sending your first event. The mapping work happens on Toplu's side, not yours.
Need a hand?
Coding is hard sometimes, and that's okay. Visit our help center or reach out directly, we're here to help.