This document is a guide to using Certain Signal to integrate with other applications by using Webhooks. It does not cover the ‘Advanced Webhooks’ product, which includes everything described here plus the use of nested JSON. Please see the separate guide to integrations using that product. Signal also integrates with Marketo, Eloqua, and Salesforce – see separate guides.
Certain Signal for Webhooks is automatically included with Certain Platform for new customers. If you’re interested in adding this or any other Signal integration to your instance of Certain, please email help@certain.com, including your account name and the Signal integration(s) you’re interested in.
Contents
- What is Signal? How does it work?
- Prerequisites
- Data-Flow Considerations
- Credentials in Target Application
- Overview of Setup Steps
- Setting up Tags
- What Are Tags?
- Setting Tags Up for an Account
- Applying Tags in an Account
- Applying Tags in an Event
- Opening Certain Signal
- Setting up a Connection
- What are Connections?
- Adding a Connection
- Setting Up Flows
- What is a “Flow”?
- The Flow List
- Configuring a Flow
- Flow Data Source
- Available sources
- Activate for
- Flow Filters
- Flow Destination
- Setting up a Destination
- Mappings
- Metrics Dashboard
- Account Insights
- The Retry Queue
- Replaying a Flow
- What is Signal? How does it work?
- Was this article helpful?
What is Signal? How does it work? Signal processes data from your events in real-time, passing it from Certain Platform to your target third-party application. The target could be any app with webhook integration, such as Slack or Google Forms. This real-time integration empowers sales and marketing teams to take intelligent, prompt action on the right event data.
Almost everything is set up at the account level. Signal processes information from the events in your account. For event-level information, this is based on the custom tags you attach to data such as Registration Statuses, as explained in this guide.
Important: Signal processes outbound information, processing information from Certain and sending it to your target application.
Prerequisites
Data-Flow Considerations
- Do you capture data in registration questions that will be synced to the third-party app to which you are integrating? If yes, apply tags to those questions. See Registration Questions.
- Do you have different data mappings based on registration status, or attendee type? If yes, apply tags to those items. See Applying Tags in an Event.
Credentials in Target Application For you to set up a Connection in Signal, the administrator of your target third-party application will need to provide you with the information described under “Adding a Connection.” For example, if your chosen Authentication Method is OAuth2, they’ll need to create an OAuth2 app in that system and provide you with the following: Endpoint, Client Id, and Client Secret.
Overview of Setup Steps Step Page On Certain Platform 1. Add tags in the account Setting Tags Up for an Account 2. Apply those tags Applying Tags in an Account 3. Add a Connection Setting up a Connection 4. Configure a Flow Setting Up Flows
Setting up Tags What Are Tags? Tags are a way of identifying event-level data using labels you set at the account level. You can then apply those tags to generic items in events, especially custom registration statuses and custom registration properties for use in Certain Signal. (Tags can be used for other purposes as well, but this guide doesn’t cover that.)
For example, your events may have several custom registration statuses in addition to the standard ones. You can apply the same Tags to more than one status, or you might choose to give each one its own Tag.
When you set up a Flow in Certain Signal to send data to your target application when an attendee’s Registration Status changes, for example, you specify the tags applicable to those statuses, not the statuses themselves. That means the flow can apply to any event in your account.
Setting Tags Up for an Account 1. As an Administrator, go to Account Settings > Management > Tags. 2. Enter a Name and a Label for the tag. 3. Select the Object(s) to which the tag can apply; for example “Registration Statuses” and/or “Custom Registration Properties”. 4. Click Add. 5. Repeat as required for as many tags as you need. 6. Important: Add enough tags to apply to all of the following that you will use in flows (see Setting up Tags): a. Registration Statuses b. Custom Registration Properties 7. Also add enough tags to apply to all of the following that you will use in filters for flows (see Flow Filters): a. Attendee Types b. Events
Applying Tags in an Account In each event from which you want information to flow through Certain Signal, apply tags to the relevant information: Registration Statuses and Registration Custom Properties. (You can also tag Attendee Types and Events to filter registration records by attendee type or event; see Flow Filters.)
Default Registration Statuses These apply to all events, so an Administrator applies the tags at the account level. 1. Go to Account Settings > Management > Registration Statuses. 2. Add one or more Tags for each status. Important: Even if you don’t use any standard registration statuses, best practice is to set up tags for all of them, but it’s essential to tag at least the “New” status (which Certain uses “behind the scenes” when first processing each registration). If you do use standard reg statuses, it’s essential that you tag them all, so that you can use them in the Flows you configure in Signal: see page 9.
Applying Tags in an Event Custom Registration Statuses 1. If any of the Flows you configure in Signal will watch or activate for changes of Registration Status (see Available sources): In each event, go to Plan > Event Setup > Custom Statuses 2. Select at least one tag for each status.
Custom Registration Properties If any of the Flows you configure in Signal will watch or activate for Custom Reg Properties (see Flow Data Source): 1. In each event, go to Plan > Configure. 2. Under Custom Registration Properties, select at least one tag for each custom reg property in the event.
Standard Registration Properties (Automatic) These tags are set up for you automatically, with names identical to the properties themselves: Complete, Badge Printed, On To Do List, Invoice Generated, and Test. You only see them in Signal, where, just like Custom Reg Properties, you can activate Flows for them (see Activate for …). There’s nothing to edit on Certain Platform.
Attendee Types (Optional– for use with filters – see Flow Filters) 1. In each event, go to Plan > Event Setup > Attendee Types. 2. Add one or more Tags for each attendee type on which you may wish to filter registrations. (See Filters on see Flow Filters.) Events (Optional– for use with filters – see Flow Filters) 1. In each event that you may wish to include in a filter (for example, to ensure that only registrations for that event are passed to your target application): 2. Go to Plan > Event Setup > Details. 3. Add one or more Tags for the event.
Registration Questions (Optional– for use with mapping Certain fields to fields your target application – see Mappings.) 1. In each event in which you use registration questions to capture data from attendees and wish to pass those answers and/or questions to your target application: 2. Go to Plan > Event Setup > Questions. 3. Select just one Tag for each question. (Selecting more could result in duplicate data in your target application.)
Opening Certain Signal
When Signal is activated for your account, the Account Settings > Implementation menu—available to Administrators—includes an extra option:
- Signal Real-Time Data Integration
Click that link to open Certain Signal in a separate window; it runs separately from Certain Platform.
Note: To return from Signal to Certain Platform at any time, click the dedicated button.
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, including to other third-party applications. (Marketo, Eloqua and Salesforce are covered in separate guides.) Each Flow (see Setting Up Flows) requires a Connection. Multiple Flows may use the same Connection. You can set up a Connection before configuring your first Flow, but you can also do so while configuring a Flow.
Adding a Connection
As an Administrator, you may set up one or more Connections for your account. You need only do so once – you can then use them in the Flows you set up.
1. Go to Account Settings > Implementation > Signal Real-Time Data Integration.
2. As noted above, Certain Signal opens in a separate window.
3. Click Connections in the left navigation panel.
4. Click Add A Connection in the Connection List page that opens.
5. Enter the details in the Connection Setup screen that opens.
- Target: Use the pre-selected value, Webhook
- Connection Name: Enter a name of your own choice. This could be just the name of the application with which you are integrating, for example
- Authentication Type: Select the authentication type to be used from the options available. (Your choice determines the other fields displayed for you to complete.)
- Basic Authentication
- URL: The endpoint to which Signal must send data.
- Content Type: application/json or x-www-form-urlencoded
- Request Method: POST or GET
- User Name: The user in the target system must have the necessary minimum permissions in that system if any are required.
- Password: That user’s password.
- Open / No Auth
- The lowest level of security
- API Key / Token
- API Key / Token: To be provided by the administrator of your target application.
- OAuth2
- All these values must be provided by the administrator of your target application.
- Grant Type: Client Credentials or Authorization Code
- Client Id and Client Secret: Unique to the OAuth2 app your administrator has set up.
- Authorization URL
- Access Token URL
- Refresh Token URL
- Scope
- Test Connection URL
- Is this a primary connection: Leave this check box clear. It’s displayed for all connections, but is only relevant to Eloqua, Marketo and Salesforce integrations requiring backwards compatibility
6. Click Save & Test.
7. If the test is successful, click Close. If it’s not, check that the values in step 5 are all correct.
Setting Up Flows What is a “Flow”? A Flow is a configuration to manage the flow of data from Certain to your target application. You create Flows from the landing page in Signal. You may configure several flows for an account, which might all use the same Connection (explained above). You only need to configure a flow once at the account level. When a flow is complete, it will start picking up data for each event in that account within about a minute.
The Flow List As an Administrator in Certain Platform, go to Account Settings > Implementation > Signal Real-Time Data Integration. Certain Signal opens in a separate browser window. The main screen in Signal is the Flow List, which lists 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 change a flow from Active to Inactive, or vice versa.
Configuring a Flow
Click ADD A FLOW to start setting up a new flow – see screenshot overleaf. The configuration consists of:
- Name
- Live or Test status
- Source
- Filters
- Destination
Live vs Test
The Live toggle determines whether the Flow is Live or Test:
- A Live Flow will pick up all live registrations in live events. It will ignore test registrations, even in live events.
- A Test Flow picks up all test registrations; that is, all registrations in test events, plus any registrations marked as Test in live events.
Best Practice: Set a new flow up as Test and test it before setting it to Live.
Flow Data Source Next, specify the Source of data for the flow (optionally applying Flow Filters). The Source of a Flow is what the Flow will watch for in your data in Certain and when it will activate based on that data. For example, it might watch for any change to a Registration Status and activate if an attendee’s status has changed to a status tagged as “Registered”.
Available sources
- Registration Create Update: When a registration is created or updated.
- Registration Status Change: When a registration’s status changes.
- Session Registration Status Change: When a registration’s session registration status changes.
Note: You can always save an incomplete Flow and complete it at a later date. As soon as a Flow is complete, it will start picking up data after the usual minute’s delay.
Activate for …
Choose what the flow should activate for by selecting one or more tags in each appropriate object’s dropdown list. The tags available for selection are those set up for that object; see Setting up Tags. For example, the tags for Registration Statuses include Registration Status tags, which you can apply to:
- standard registration statuses at the account level
- custom registration statuses at the event level
Flow Filters
You can filter the data going into a flow by selecting fields in any of these three filter types: Event fields, Profile fields, and Attendee Type tags. The flow will only include a registration if it meets the rule(s) specified in the filter.
- Event
- Available fields: standard event fields (e.g., Event Code), custom event fields, event tags
- Profile
- Available fields: standard profile fields (e.g., Position), custom profile fields
- Attendee Type Tags
- Available fields: tags that can be applied to Attendee Types
Flow Destination Select Webhooks from the integrations set up by Certain for your account. (You may have this and others to choose from.)
Setting up a Destination 1. Give the Destination a Name of your choice 2. Select the Connection to use Note: You can instead click New Connection to add a connection; the process to set one up is the same as described on Setting up a Connection. 3. Select Webhook as the Action for this connection. 4. Select or add the mappings to use, as described next.
Mappings
Select or set up a set of mappings. You can have two: one for the Payload and (if required) one for the Http Header. The setup process is the same for each:
- Give the mapping a name of your choice.
- Obtain a sample JSON from the source.
- For each of the target fields you identify in that JSON, enter the name of that target field and click Add.
- Click to select the “source” field in Certain that matches that target field.
- The Certain fields you can choose from as the source of the data going into each target field in your target application will include some of these, depending on what your flow will activate for: Profile Standard Fields; Profile Custom Fields; Registration Standard Fields; Registration Custom Question Tags; Registration Standard Properties; Account Standard Fields; Event Standard Fields; Event Custom Fields; Flow Fields; Macros.
- You can concatenate multiple source fields for the same target field, and you can add fixed text.
- To make a target field required, select the required checkbox.
- If a required field is missing, there will be a validation error when the flow tries to update your target application.
- If a required field is missing, you should not edit that in The Retry Queue.
- To delete a source field, click the x after its label.
- If you’ve selected a mapping, two more buttons are enabled: Edit Mapping and Preview Mapping.
- Save the mapping.
Metrics Dashboard To see the statistics available in Signal, click Metrics in the left navigation panel when looking at flows. The choices in the new navigation panel depend on the flows and their targets. The first item will be Insights. Other links will be Webhook Posts and Account Insights.
Account Insights
Choose between Live Flows or Test Flows. Set the period for which you want to see the data (e.g., the last 15 minutes, 1 hour, 4 hours, or a number of days). There are three tabs: Summary, Troubleshooting, and Activity Feed.
- Summary: This is the default tab. The figures depend on the flows and actions. You can drill down into details by clicking numbers. Examples include Unique Registrations and Changes Processed.
- Troubleshooting: This tab shows information useful for troubleshooting. It includes In Retry Queue, Total Retried, Retried Abandoned, Validation Errors, Retry Activity, Retry Processing Category, Connection Activity.
- Activity Feed: This tab lists processed registrations with details like Registration Code, Event, Flow, and success/failure status. It is a rolling history by date.
The Retry Queue When an action fails, it joins the Retry Queue and will be retried. A maximum of three automatic retries applies per action. If an item is resolved, it will be removed from the queue. If not, contact your administrator or ask Certain for help. The retry interval depends on the reason's severity.
Filtering the Queue You can filter the Retry Queue by Integration (usually Webhooks), Status (All Statuses, Retry, Error, Failed, Done), and Category (All Categories, General, System, Config, Certain API, Connection, etc.).
Submitting to the Queue Click an item in the Retry Queue to see its full details. If you can solve the issue, click Submit to Retry Queue to move the item to the front of the queue.
Replaying a Flow If you change an aspect of a flow while it has been running, you may want to replay that flow for the same registrations as before. This is not done directly by the UI. You can ask Certain to arrange it. You may specify a date range or an event.
Was this article helpful? 0 out of 0 found this helpful Have more questions? Submit a request Return to top
Related articles
- Signal Integration with Advanced Webhooks Guide
- Signal Integration with Eloqua Guide
- Data Extraction Guide
- Comments
0 comments
Please sign in to leave a comment.