Skip to main content

​
Overview

Campaign Mapping lets you assign keywords to workspaces that represent partial matches of campaign names from your third-party sequencer. When a keyword matches a campaign name, RevyOps automatically assigns that campaign to the specified workspace. All related data from the matched campaign then appears in that workspace and its reports. Campaign Mapping is under Settings → Connect and is only available to Agency admins.

​
Webhooks

The Webhooks section shows the webhook URL for each supported sequencer: Instantly, EmailBison, Smartlead, Lemlist, Sendkit, and HeyReach. Select a sequencer from the list on the left to see its webhook URL, and click the copy icon to copy it to your clipboard.

​
Setting Up a Workspace’s Mapping

The workspaces table lists every workspace, its configured keywords, and which integrations have mapping configured for it. To edit a workspace’s mapping, click the pencil icon in that workspace’s row. In the Edit Campaign Keywords dialog you can:
  1. Add a keyword: type it into the New keyword field and click Add, or press Enter.
  2. Remove a keyword by clicking the delete icon next to it.
  3. Choose which Integrations with mapping should receive events for this workspace. If the keyword is found in the campaign name, the event is forwarded to the selected integrations.
Changes save automatically when you close the dialog. A keyword matches when the campaign name contains it exactly, capital letters included. The keyword Acme matches “Acme Q3 Outbound” but not “ACME Q3 Outbound”. An event sent to one of these webhooks whose campaign name matches no workspace’s keyword, or matches only workspaces that haven’t selected that integration, goes to no workspace at all, and nothing reports an error. A campaign name that matches keywords for two workspaces goes to both, so avoid keywords that sit inside other workspaces’ campaign names, such as Co inside “Acme Co”. Two sequencers route some events differently:
  • An EmailBison event that carries a workspace name is matched on the whole workspace name, ignoring capitals, and goes to the first RevyOps workspace with the same EmailBison API URL whose keywords include it. Use the EmailBison workspace’s full name as the keyword, such as Acme Outbound for the EmailBison workspace “Acme Outbound”.
  • HeyReach tag events, such as a lead tagged Interested, carry no campaign name. They go to the workspaces that have messaged that lead through HeyReach, whatever the keywords say.
If an agency-level webhook is configured, all events sent directly to the workspace’s webhook are ignored to avoid duplicates.

​
Configuring Integration Labels

Before events can be tagged, each selected integration needs its label mapping configured. If an integration you selected for a workspace isn’t configured yet, a warning appears saying that integration’s labels aren’t configured and events with tags will fail, along with a Configure Integration button. Clicking Configure opens a two-step dialog:
  1. Enter your API key (and, for EmailBison, the API URL) for that integration, then click Verify & Fetch Labels.
  2. Classify each status or label the integration returns: mark which ones count as Interested leads, and which should trigger Do Not Contact (for integrations that support it). RevyOps pre-suggests likely “interested” labels based on common keywords (like “interested,” “hot lead,” “meeting booked”) and likely negative ones (like labels starting with “not,” “un,” “lost,” or “wrong”).
Lemlist only supports classifying events for Do Not Contact; it doesn’t have an interested-label step. Click Save Labels to finish. Once saved, the workspace’s row in the table shows that integration as configured.