Signal Integration with Advanced Webhooks Guide

What is Signal? How does it work?

• Signal processes data from events in real time.
• Signal passes data from Certain Platform to the target third-party application.
• A target third-party application can be any app with webhook integration.
• Examples of target applications include Slack and Google Forms.
• This real-time integration empowers sales and marketing teams to act promptly on the right event data.
• Almost everything is set up at the account level.
• Signal processes information from events in the account.
• For event-level information, Signal uses the custom tags attached to data such as Registration Statuses.
• Signal processes outbound information and sends it to the target application.

Prerequisites

• Data-Flow Considerations
• Do you capture data in registration questions that will be synced to the third-party app you are integrating?
• If so, apply tags to those questions (see “Applying Tags”).
• Do you have different data mappings based on registration status or attendee type?
• If so, apply tags to those items (see “Applying Tags”).
• Credentials in Target Application
• To set up a Connection in Signal, the administrator of your target third-party application must provide the information described under “Adding a Connection.”
• If the chosen Authentication Method is OAuth2, they’ll need to create an OAuth2 app in that system and provide Endpoint, Client Id, and Client Secret.

Overview of Setup Steps

• On Certain Platform: Add tags in the account.
• Apply those tags.
• In Certain Signal: Add a Connection.
• In Signal: Configure a Flow.

Setting up Tags

What Are Tags?

• Tags identify event-level data using labels set at the account level.
• Tags can be applied to registration statuses and custom registration properties.
• Tags can be used for other purposes, but this guide does not cover that.
• When a Flow sends data based on a Registration Status change, you specify the tags, not the statuses themselves.
• This allows the Flow to apply to any event in the account.

Setting Tags Up for an Account

• As an Administrator, go to Account Settings > Management > Tags.
• Enter a Name and a Label for the tag.
• Select the Object(s) to which the tag can apply (e.g., Registration Statuses and/or Custom Registration Properties).
• Click Add.
• Repeat as needed for multiple tags.
• Add enough tags to cover:
• Registration Statuses
• Custom Registration Properties
• Attendee Types (optional for filters)
• Events (optional for filters)

Applying Tags in an Account

• In each event, apply tags to relevant information: Registration Statuses and Registration Custom Properties.
• You can also tag Attendee Types and Events for filtering registrations.

Default Registration Statuses

• These apply to all events; an Administrator applies the tags at the account level.
• It is recommended to tag all standard statuses, especially the New status.

Custom Registration Statuses

• If any Flows watch or activate for Custom Reg Statuses, tag at the event level.

Custom Registration Properties

• If any Flows watch or activate for Custom Reg Properties, tag at the event level.

Standard Registration Properties (Automatic)

• These tags are set up automatically with names identical to the properties: Complete, Badge Printed, On To Do List, Invoice Generated, and Test.

Attendee Types

• (Optional for use with filters) Tag Attendee Types.

Events

• (Optional for use with filters) Tag Events.

Registration Questions

• (Optional for use with mapping Certain fields to fields in your target application) Tag Registration Questions.

Opening Certain Signal

• When Signal is activated for your account, the Account Settings > Implementation menu adds an extra option: Signal Real-Time Data Integration.
• Signal opens in a separate window.

Setting up a Connection

What are Connections?

• A Connection in Certain Signal specifies how to connect to your target application.
• You can have multiple connections for different target applications.
• Each Flow requires a Connection.
• You can set up a Connection before configuring a Flow or during Flow configuration.

Adding a Connection

• As an Administrator, go to Account Settings > Implementation > Signal Real-Time Data Integration.
• Open the Connections section.
• Click Add A Connection.
• Enter the details in the Connection Setup screen.
• Target: Advanced Webhook.
• Connection Name: Provide any suitable name (e.g., the application name).
• Authentication Type: Choose from Basic Authentication, Open / No Auth, API Key / Token, OAuth2.
• For each authentication type, provide the required fields (URL, Content Type, Request Method, credentials, etc.).
• Optional: Test Connection URL.
• Optional: Mark as primary connection (relevant to specific integrations).
• Save and Test; if successful, Close; if not, verify values.

Setting Up Flows

What is a “Flow”?

• A Flow manages the flow of data from Certain to the target application.
• Flows are created from the Signal landing page.
• You may configure several flows for an account.
• Flows may share the same Connection.
• A Flow becomes active after configuration and begins processing data about a minute after completion.

The Flow List

• The Flow List shows all flows.
• The Status column shows whether a flow is completely set up.
• The Active column shows whether the flow is running; use the toggle to switch between Active and Inactive.

Configuring a Flow

• Click ADD A FLOW to start.
• The configuration includes:
• Name
• Live or Test status
• Source: What data the Flow watches
• Filters: Optional filters to narrow data
• Destination: Where the data goes in the target app
• Live vs Test
• A Live Flow collects live registrations in live events; it ignores test registrations.
• A Test Flow collects test registrations.
• Best practice: set up as Test, test it, then set to Live.

Flow Data Source

• The Source determines what the Flow watches for in Certain Platform.
• Available sources include:
• Registration Create Update
• Registration Status Change
• Session Registration Status Change
• Event Create Update
• Activate for …
• Choose one or more tags to activate for Registration Statuses, Registration Properties, etc.
• If watching for Registration Status Change, activate for Registration Statuses.
• If watching for Session Registration Status Change, activate for Session Registration Statuses.
• If watching for Event Create Update, activate for Event Statuses.

Flow Filters

• Flow Filters narrow the data by Event fields, Profile fields, and Attendee Type tags.
• A registration is included only if it meets the filter rules.
• Event fields include standard and custom fields and event tags.
• Profile fields include standard and custom fields.
• Attendee Type Tags include available tags for Attendee Types.

Flow Destination

• Select Advanced Webhooks from the integrations available for the account.

Setting up a Destination

• Provide a Destination Name.
• Select the Connection to use.
• Use New Connection if creating one.
• Select Advanced Webhook as the Action.
• Choose or create Mappings.
• Mappings define how each target field maps to a source field.

Mappings

• A mapping pairs target fields with source fields in Certain.
• You can have two mappings: one for Payload and one for Http Header if needed.
• To create a mapping, give it a descriptive name.
• Choose Root Element Type (Object is default; Array of Objects if needed).
• You can paste a sample JSON to parse the structure or map fields manually.
• You can map multiple source fields to one target field if needed.
• You can apply transformations such as lower case, Proper Case, UPPER CASE, Trim.
• You can mark fields as required; missing required fields cause validation errors.

Example Mapping from Pasted JSON

• If you choose Parsed Structure, Signals parse an example JSON to determine fields.
• You can map source fields to target fields as shown in the example.
• You can create a Mapping and Preview it.

Metrics Dashboard

• The Metrics page shows statistics for flows.
• There are tabs: Summary, Troubleshooting, Activity Feed.
• Summary includes:
• Changes Processed
• Unique Registrations
• Actions Triggered
• Leads Created
• Leads Updated
• Registration Activity in Certain
• Processing Status (a pie chart)
• Troubleshooting includes:
• In Retry Queue
• Total Retried
• Retried Abandoned
• Validation Errors
• Retry Activity
• Retry Processing Category
• Connection Activity
• The Activity Feed shows a rolling history of processed registrations.

The Retry Queue

• When an action fails, it may join the Retry Queue.
• A failed action can be retried up to three times.
• The Retry Queue can be viewed under Retry in the Flows page.
• Causes of failure include untagged statuses or a down connection.
• To fix failures, adjust tags or restore the flow to active and retry.

Replaying a Flow

• If a Flow has been changed during operation, you can request a replay for prior registrations.
• This action is performed by request, not directly by you, and may include date ranges or events.

---

[JSON-LD] { "@context": "https://schema.org", "@type": "TechArticle", "headline": "Signal Integration with Advanced Webhooks Guide", "description": "Guide to integrating Certain Signal with external apps using Advanced Webhooks, including tags, connections, and flows.", "datePublished": "2026-02-08", "contentFreshness": "assumed-current", "inLanguage": "en", "keywords": ["Advanced Webhooks", "Signal", "Connections", "Flows", "Tags", "Mappings", "Retry Queue"], "about": { "@type": "SoftwareApplication", "name": "Certain Signal", "applicationCategory": "Automation/Integration Platform", "description": "Real-time data integration to third-party apps via webhooks" }, "mainEntity": { "@type": "Thing", "name": "Signal Advanced Webhooks" }, "geo_quality": { "fluency_applied": true, "issues_fixed": ["vague_referents", "long_sentences", "missing_definitions"], "rewrite_count": 5 } } [/JSON-LD]