Connection Creator is not a separate tool. It is the engine behind every place in PalDock that talks to an outside system. A scenario always belongs to one of four contexts, and the context decides what starts it, what data it receives, and whether anyone is waiting for the answer.
Integration
Sends a lead to an advertiser and processes the answer. Started when a lead reaches an offer, either directly or through a pingtree. The scenario receives the lead data and gives back the result: accepted or rejected, the redirect URL, the advertiser’s own ID for the lead. See more here.
This is the most common use, and it is the one the Integration Library is built for.
Structure
Runs inside the form itself, while the lead is still being created. See more here. Three purposes:
- Validation checks a value while the form is being filled in and can block the submit.
- Modification fills a field with a value from an external service. See Modification.
- Autocomplete suggests values to the visitor while typing. See AutoComplete.
All three run while the visitor is waiting, so they must be fast. See Limits and timeouts.
Tracking
Handles conversion and status data moving in and out of PalDock. Two directions:
- Incoming postback processes a conversion or status update sent to PalDock.
- Outgoing postback sends conversion and status data from PalDock to affiliates or other systems, and can also poll an advertiser for a result.
Both run in the background. Nothing is waiting for them, so they can take longer and can pause and resume. See more here.
Feed
Pulls product or offer data from an external source and brings it into PalDock. Runs in the background on its own schedule.
Where scenarios live
All scenarios are managed in the Tools menu, in the respective section based on the context they belong to.
To add one, click Add and choose either a custom integration or a prebuilt one from the Library of Integrations. If you use global fields, most library integrations are ready after a single click.
How scenarios are triggered
The context decides what starts a scenario:
- Integration starts when a lead is sent to an offer, either directly or through a pingtree.
- Structure starts while data is being entered: a lead in a form, a partner during onboarding, or a record during feed ingestion.
- Incoming postback starts when PalDock receives a call from an external system.
- Outgoing postback starts when something happens inside PalDock, for example a new conversion or a status change.
- Feed starts on its own schedule.
