Skip to main content
Part of the partner integration guide.

​
Overview

A Partner to Extole integration carries activity from an outside platform into Extole: purchases, shipments, cancellations, account openings, or the eligibility of a group of customers. It is one of the categories in Integration Categories, and the one with the most moving parts, because the work is split between the partner platform and the Extole campaign. The pages below follow one arriving event from the partner’s system to the moment it becomes something Extole can attribute, reward, and report on. Read them in that order — each stage assumes the one before it.

​
The Stages

Delivery and normalization are alternatives more often than they are companions. A platform whose sending code you write sends Extole-shaped events and needs no prehandler; a platform that emits only its own fixed webhook needs a prehandler and has no sender to build. Mapping is required either way. Audience membership is the outlier. It travels the same direction but carries no business events at all, so it skips delivery, normalization, and mapping entirely and is the one Partner to Extole shape that needs a credential.

​
Two Event Vocabularies

Every stage above depends on keeping two sets of names apart, and confusing them is the most common way a build fails silently:
  • The partner’s wire name — whatever the platform calls the event, such as partner_order_created. It belongs on the input_event trigger rule, or is the name a prehandler rewrites.
  • The canonical Extole name — converted, shipped, canceled, account_opened. It belongs on the business event, because programs and reports read it.
Never rename a business event to match a partner. A rule that still listens for a name nothing produces never matches, and reads as correct in the component tree.

​
What This Direction Does Not Need

A Partner to Extole integration creates no reward supplier, webhook, or client key. Those belong to the Extole to Partner direction — see Build an Extole to Partner Integration. Audience membership is the single exception, needing a credential the partner authenticates with. Incoming CSV or SFTP files are not this tree either. Install the File Integration extension instead.