Campaign Console

Use the Campaign Console when you want one place to run a launch without mixing every campaign type into one list. Marketing Campaigns, Site Campaigns, Email Campaigns, and Automations stay separate so each workflow keeps the right setup, targeting, content, and stats.

Open Product Suite, choose a workspace handle, then go to Publish -> Campaigns. Direct route pattern:

https://app.10x.in/apps/publish/campaigns?handle={handle}

What You Can Manage

Before You Start

You need:

• A Product Suite user with operator or owner access to the handle.
• A selected handle in Product Suite.
• At least one Marketing Campaign if you want umbrella rollups and attachments.
• For Email Campaigns, a verified sender profile and any reusable email templates you plan to use.
• For Site Campaigns, the 10x public SDK installed on the page where the Site Campaign should appear.

Related setup guides:

• Email Sending Through 10xDotIn
• Campaign Email Automation Through 10xDotIn
• Campaign Funnel Workflow

Recommended Workflow

1. Create or choose the Marketing Campaign

   Use the Marketing Campaign as the umbrella for launch goals, tagged links, page handoff, and rollup reporting.

2. Add Site Campaigns for onsite experiences

   Configure lead capture, banners, messaging, popups, custom HTML, or event tracking for the pages where visitors land.

3. Add Email Campaigns for broadcasts

   Build the broadcast email, test it, attest recipient consent, and send it separately from automations.

4. Attach related work to the Marketing Campaign

   Attach Site Campaigns, Email Campaigns, automations, links, pages, and ad mappings so the Marketing Campaign detail view can summarize performance.

5. Review stats

   Use the detail panel and performance summary for traffic, lead, conversion, site, and email activity.

Marketing Campaigns

Marketing Campaigns are umbrella containers. They should describe the launch or acquisition effort, not store onsite HTML or email body content.

Use Marketing Campaigns to:

• Track the goal and status of a launch.
• See how many links are tagged with the campaign ID.
• Open the campaign page editor.
• Open campaign automation rules.
• Review health checks and recent session state.
• Aggregate attached Site Campaign and Email Campaign performance.

Common actions in the Marketing Campaign table:

Site Campaigns

Use Site Campaigns for onsite experiences. Examples:

• Lead capture block.
• Offer banner.
• Popup.
• Inline message.
• Coupon capture prompt.
• Custom HTML widget.
• Custom event tracking.

Create A Site Campaign

1. In Campaign Console, scroll to Site Campaigns.
2. Select New.
3. Enter a stable Site campaign ID such as spring-lead-capture.
4. Enter a Name.
5. Choose the Type: LEAD_CAPTURE, MESSAGE, BANNER, POPUP, OFFER, or CUSTOM.
6. Optionally set Marketing campaign ID to attach it to an umbrella Marketing Campaign.
7. Choose placement.
8. Paste Targeting JSON.
9. Add Custom HTML, CSS, JavaScript, and Events JSON as needed.
10. Select Save.
11. Select Activate when the campaign is ready.

Site Campaign Placements

Example placement:

{
  "type": "CAMPAIGN_DETAIL_PAGE",
  "campaignId": "spring-launch",
  "pageSlug": "spring-launch"
}

Site Campaign Targeting JSON

Site Campaigns use simple rule groups:

{
  "match": "ALL",
  "rules": [
    { "field": "device", "operator": "in", "values": ["DESKTOP", "MOBILE"] },
    { "field": "source", "operator": "in", "values": ["google"] },
    { "field": "path", "operator": "matches", "values": ["/pricing/*"] }
  ]
}

Supported fields:

Use match: "ALL" when every rule must match. Use match: "ANY" when any rule can match.

Custom HTML, CSS, JavaScript, And Events

For CUSTOM Site Campaigns, the editor accepts:

• Custom HTML for the onsite block.
• CSS for styling that block.
• JavaScript for runtime behavior.
• Events JSON for click, form, visibility, scroll, dwell, or custom-dispatch events.

Example event:

[
  {
    "name": "offer_clicked",
    "selector": "[data-10x-event='offer_clicked']",
    "trigger": "click",
    "metadata": {
      "offer": "spring-launch"
    }
  }
]

Supported event triggers:

Email Campaigns

Use Email Campaigns for broadcast email. Do not use this lane for OTP, coupon fulfillment, lead-capture follow-up, or conversion follow-up. Those remain Automations.

Create An Email Campaign

1. In Campaign Console, scroll to Email Campaigns.
2. Select New.
3. Enter an Email campaign ID such as spring-broadcast.
4. Enter a Name.
5. Enter a ready Sender ID.
6. Choose the Purpose: PRODUCT_NOTIFICATION or TRANSACTIONAL_API.
7. Optionally enter a Marketing campaign ID to attach the broadcast to a Marketing Campaign.
8. Choose Content mode.
9. Paste Audience targeting JSON.
10. Add template details or raw email HTML.
11. Select Save.
12. Select Preview.
13. Send a test email.
14. Check Consent attested for this audience.
15. Select Send broadcast.

Audience Targeting JSON

The first release can store several audience fields, but broadcast send resolution is explicit-recipient first. Include emails rules for any campaign you intend to send now.

{
  "match": "ALL",
  "rules": [
    {
      "field": "emails",
      "operator": "in",
      "values": ["buyer@example.com", "lead@example.com"]
    }
  ],
  "exclusions": [
    {
      "field": "emails",
      "operator": "in",
      "values": ["do-not-email@example.com"]
    }
  ]
}

Supported stored fields:

Suppression lists are applied during send. Suppressed addresses are counted as excluded recipients.

Email Content Modes

Raw HTML example:

{
  "mode": "RAW_HTML",
  "subject": "Spring launch is live",
  "html": "<p>See the new offer.</p>",
  "text": "See the new offer.",
  "variables": {
    "firstName": "Asha"
  }
}

Template mode example:

{
  "mode": "TEMPLATE",
  "templateId": "tmpl_spring_launch",
  "templateVersion": 1,
  "variables": {
    "firstName": "Asha",
    "offerName": "Spring Launch"
  }
}

Preview, Test Send, And Broadcast Send

By default, the system requires a test send before broadcast send. Operators can only send after they attest consent for the audience.

Automations

Use the Rules action on a Marketing Campaign for campaign-scoped automations:

• Lead-captured email rules.
• Delayed lead follow-up.
• Conversion-triggered email.
• OTP/lead verification setup.
• Coupon fulfillment email workflow.

Automations are intentionally separate from Email Campaign broadcasts. This prevents a one-time broadcast from being confused with event-triggered lifecycle messaging.

Performance And Stats

The Campaign Console combines several reporting sources:

Stats are eventually consistent. A broadcast can show queued or sending state before downstream delivery events arrive.

API Reference For Power Users

Use Product Suite first. Use APIs when you need automation or bulk setup.

Site Campaigns

Email Campaigns

Marketing Campaign Attachments

Troubleshooting