Integrations.
Named systems and how their data behaves. Registration platforms, lead retrieval, floorplan tools, CRM, ERP, exhibitor portals, and the export you will want on the way out.
30 articles · Integrations
- How to plan a Cvent data export you can actually reusecvent data exportA Cvent data export is only reusable if registration type, source code and cancellation status survive the crossing. How to plan one before you pull it.
- Reading the Swapcard API rate limits before you build the nightly pullswapcard api rate limitsThe Swapcard API rate limits are priced in points, not requests, so a nightly attendee pull has to be costed field by field before you write the loop.
- Loading MYS exhibitor data without losing the booth linkmap your show exhibitor dataMap Your Show exhibitor data loads cleanly and the booth link does not. Model the exhibitor key and the booth key separately before the join is written.
- Planning an a2z Events data export across several shows and yearsa2z events data exportAn a2z Events data export across several editions is mostly a booth numbering problem. Separate a renumbered hall from an exhibitor who genuinely moved.
- What the ExpoFP floorplan API gives you and what it does notexpofp floorplan apiThe ExpoFP floorplan API sends exhibitors, booths and extras into a plan. Treat it as a geometry source and keep the exhibitor master somewhere else.
- Sizing an event data sync against Salesforce API limitssalesforce api limitsSalesforce API limits are a 24 hour allowance plus a licence multiplier. Size a registration sync against both before you write one call per record.
- Working inside HubSpot API rate limits when a registration file landshubspot api rate limitsHubSpot API rate limits set a burst ceiling per ten seconds and a daily cap per account. Size a 30,000 contact registration upload against both of them.
- Handling Dynamics 365 API throttling during a show week data loaddynamics 365 api throttlingDynamics 365 API throttling is enforced per user over a five minute window, so one integration account becomes the ceiling on your busiest scanning minute.
- Questions to settle before a Marketo event integration goes livemarketo event integrationA Marketo event integration lives inside a daily call quota, a twenty second rate limit and a concurrency ceiling. Time one 5,000 lead push before scheduling.
- Pulling Stova registration data into a portfolio level reportstova registration dataStova registration data rolls up across a portfolio only if registration type means the same thing in every show. Count the near duplicates before you build.
- What a Grip matchmaking export tells you about meeting demandgrip matchmaking exportA Grip matchmaking export mixes requests, acceptances and held meetings in one table, and the permission settings decide who could be recommended at all.
- Using the Brella REST API to pull meeting and lead databrella rest apiA Brella REST API pull can carry meeting ratings as well as bookings, which is the one field that says something about quality rather than volume.
- Mapping an ExpoPlatform data export onto your own event schemaexpoplatform data exportAn ExpoPlatform data export arrives with one identifier space across modules, which helps until you ask which of those identifiers survives the next edition.
- Joining onPeak housing data to the registration fileonpeak housing dataJoining onPeak housing data to the registration file usually falls back to email, and email drops the guests whose rooms were booked by somebody else.
- Cvent Passkey reservation data and what to settle before you model room blockscvent passkey reservation dataCvent Passkey reservation data supports several different pickup numbers, and the one your report shows is rarely the one the hotel invoice was computed from.
- Getting GES exhibitor ordering data out and lined up with your booth listges exhibitor ordering dataGES exhibitor ordering data is keyed on the contractor's own account number, so matching it to your booth list by company name leaves a fifth unattributed.
- What a Zuant lead capture export looks like when it reaches the CRMzuant lead capture exportA Zuant lead capture export passes a filter and release step before the CRM sees it, and that is where organiser and exhibitor lead counts diverge.
- Syncing an association management system with the show registration platformassociation management system syncAn association management system sync copies a membership status that is effective dated, into a registration platform that stores it as a flag with no date.
- Choosing webhooks versus polling for an event registration feedwebhooks versus pollingWebhooks versus polling is a latency decision rather than a completeness one, and an event registration feed usually needs both running side by side.
- Making an SFTP file drop integration survive a badly timed uploadsftp file drop integrationAn SFTP file drop integration fails silently when the loader reads a file mid write, and the fix is atomic delivery plus a manifest carrying row counts.
- Why idempotency keys matter when you push registrations into a CRMidempotency keysIdempotency keys let a registration push retry safely after a timeout. Without one, the retry writes every row the first attempt already committed.
- Finding the API history limits in your event systems before a five year backfillapi history limitsAPI history limits decide how much of a five year backfill you can retrieve. Most event platforms show more history in the interface than the API returns.
- Surviving API schema versioning when a vendor upgrades mid seasonapi schema versioningAPI schema versioning decides whether a vendor upgrade quietly breaks your event pipeline. Pin every integration to a version and diff the payloads you store.
- A rate limit backoff strategy that holds up on the busiest registration dayrate limit backoff strategyA rate limit backoff strategy decides whether a registration surge slows your sync or stops it. Exponential backoff with jitter, and Retry-After, is the answer.
- Getting usable sandbox and test data out of an event platformsandbox and test dataSandbox and test data from an event platform rarely resembles production. Build a synthetic file at real shape and volume before the integration meets a sale.
- Setting up single sign on across event systems without breaking show weeksingle sign on event systemsSingle sign on across event systems only removes access if local passwords are disabled too. Count who can sign in to your registration platform today.
- Writing data export rights into an event platform contractdata export rightsData export rights have to be written into the contract, because privacy law covers personal data and leaves booth history, priority points and scores behind.
- Testing for vendor lock in before you renew an event platformvendor lock inVendor lock in on an event platform lives in identifiers and history. Run an exit test a year before renewal and try rebuilding last year's post show report.
- Reconciling two systems that disagree about the same registration recordreconciling two systemsReconciling two systems that disagree about a registration starts with one frozen timestamp and a named bucket for every difference. The gap is structural.
- What belongs in an integration runbook for an event tech stackintegration runbookAn integration runbook names an owner, a credential expiry, a schedule and an expected row count for every connection in the event stack, on one page each.