How is data synced between systems?

High Confidence (70%)
How is data synced between systems?

Short answer: Certain syncs data using two main methods — Signal for real‑time, tag‑driven outbound flows to external systems (Marketo, Eloqua, CRMs, etc.), and API Fetch for scheduled/polled inbound imports. In addition, Platform → Touchpoint syncs use account‑level tags on Conference Custom Fields and Registration Statuses to map specific fields into the Touchpoint app.

Details — how each works

  • Signal (real‑time outbound)
  • Real‑time event data is routed by configurable Flows in Certain Signal.
  • Flows are controlled by account‑level tags you apply to registration statuses, custom properties, questions, attendee types, or events; those tags determine which records and when they are sent.
  • Signal requires a Connection (OAuth2 or Basic credentials) to the external system and supports per‑flow mapping/transformations.
  • Examples: guides for connecting to Eloqua and Marketo show creating Connections and Flows to push registrations, status changes, and activity in real time.
  • Source: Signal Integration with Eloqua Guide, Signal Integration with Marketo Guide, Signal infographic.
  • API Fetch (scheduled inbound or custom polling)
  • API Fetch pulls data from external systems on a schedule (REST endpoints), supports pagination, incremental checkpointing, and JSON schema transformations (Jolt), then maps inbound records into Certain actions (e.g., Bulk Registration Upsert).
  • Useful for importing large datasets or periodic syncs from registration systems, CRMs, or marketing systems.
  • Source: API Fetch — Eloqua step‑by‑step configuration.
  • Platform → Touchpoint mapping (Platform custom fields → Touchpoint)
  • Use account tags such as Touchpoint: Related Link on Conference Custom Fields to tell the integration server which fields to sync to Touchpoint.
  • The integration recognizes the FIRST link in a tagged custom field (Title → Related Link title; URL → Related Link URL). If you need multiple links, put each in its own custom field (one custom field per related link).
  • If you add the tag after integration activation, run a mass action on sessions so the integration server reprocesses and syncs them.
  • For registrant syncs, apply the Touchpoint: Synced tag to Registration Statuses that should be pulled into Touchpoint.
  • Source: Session Related Links: Syncing from Platform to Touchpoint; Syncing Registrants to Touchpoint from Platform.
  • Data transformation & governance
  • You can transform and map data before sending/after receiving (Jolt transforms are used in API Fetch; Signal supports mapping and tagging).
  • Tags provide governance and let you apply consistent flows across events without editing each event’s mapping.

Important operational notes

  • Tags are central: set them at the account level and apply them to events/items you want included in flows.
  • For Touchpoint related links, only the first link in a tagged custom field is recognized — multiple links require separate fields.
  • For API Fetch, configure pagination, checkpointing (initial checkpoint value for the first run), and timeouts so incremental pulls resume correctly.
  • Authentication: Signal connections use OAuth2 (recommended) or Basic credentials depending on the external system.

Sources

Question for you Which external system are you trying to sync with (Touchpoint, Eloqua, Marketo, CRM, or something else) so I can give step‑by‑step guidance?