--- title: "Campaigns" description: "A non-technical overview of Campaigns in RevCent, focused on how they organize sales, customers, related commerce activity, reporting, AI workflows, and Organization/User visibility boundaries." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/Campaign.md" relationships: - name: "Organization" url: "https://revcent.com/documentation/markdown/ecosystem/feature/Organization.md" - name: "User" url: "https://revcent.com/documentation/markdown/ecosystem/feature/User.md" technical_links: web_app: "https://kb.revcent.com/en/management/campaign" api: section: "https://revcent.com/docs/api/v2#section-campaigns" operations: - name: "Get Campaigns" operation_id: "GetCampaigns" operation: "https://revcent.com/docs/api/v2#operation-GetCampaigns" schema: "https://revcent.com/documentation/files/api/operation/GetCampaigns.json" - name: "Create A Campaign" operation_id: "CreateCampaign" operation: "https://revcent.com/docs/api/v2#operation-CreateCampaign" schema: "https://revcent.com/documentation/files/api/operation/CreateCampaign.json" - name: "Get A Campaign" operation_id: "GetCampaign" operation: "https://revcent.com/docs/api/v2#operation-GetCampaign" schema: "https://revcent.com/documentation/files/api/operation/GetCampaign.json" - name: "Edit A Campaign" operation_id: "EditCampaign" operation: "https://revcent.com/docs/api/v2#operation-EditCampaign" schema: "https://revcent.com/documentation/files/api/operation/EditCampaign.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewCampaign.md" operations: - name: "Get Campaigns" operation_id: "GetCampaigns" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetCampaigns.md" available_via_ai: true - name: "Create A Campaign" operation_id: "CreateCampaign" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateCampaign.md" available_via_ai: true - name: "Get A Campaign" operation_id: "GetCampaign" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetCampaign.md" available_via_ai: true - name: "Edit A Campaign" operation_id: "EditCampaign" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditCampaign.md" available_via_ai: true bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json" bigquery_tables: - "campaign" --- # Campaigns Campaigns are a central RevCent feature used to organize commerce activity. A Campaign gives RevCent a consistent way to group sales, customers, and the records created from those sales and customers. When a business wants to separate activity by brand, store, funnel, website, product line, operating unit, or business segment, Campaigns are one of the primary tools used to do that. The practical idea is: ```text Campaign = business/data segment for commerce activity Sale and Customer activity = organized under Campaign context Related records = understood through the Campaign context of the sale/customer flow ``` Campaigns are especially important because the RevCent Knowledge Base describes Campaigns as central to RevCent and says every sale and associated entity is created with the Campaign attribute. This makes Campaigns a core filtering and segmentation layer across RevCent. --- ## Why Campaigns Are a Feature Campaigns are a feature because they are configurable account-level structures created and managed by the business. A Campaign is not merely a one-time transaction record. It is a reusable organizational layer that can be selected, filtered, associated with Organizations, used in reports, used in event filters, and used as a consistent business context for sales and customer activity. Conceptually: ```text Business creates Campaign ↓ Campaign is used by sales/customer workflows ↓ Related records carry or inherit Campaign context ↓ RevCent users, reports, AI workflows, and visibility rules can filter by Campaign ``` This makes Campaigns different from items such as sales, transactions, customers, shipments, or fraud detections. Those records are created as business activity happens. A Campaign is the configurable structure used to organize that activity. --- ## Technical Links | Area | Link | |---|---| | Web App | `https://kb.revcent.com/en/management/campaign` | | API | `https://revcent.com/docs/api/v2#section-campaigns` | | MCP / AI | `https://revcent.com/documentation/markdown/mcp/operation/OverviewCampaign.md` | | BigQuery Schema | `https://revcent.com/documentation/files/bigquery/dataset.json` | | BigQuery Tables | `campaign` | --- ## Core Purpose The core purpose of a Campaign is to provide a durable business context for commerce records. Campaigns help answer questions such as: - Which business, brand, store, funnel, or operating segment generated this activity? - Which Campaign should this sale belong to? - Which Campaign should this customer be associated with? - Which Campaign should a report filter by? - Which Campaign should an AI Assistant event filter watch? - Which Campaign should lower-level users be allowed to see through an Organization boundary? Campaigns are useful because ecommerce activity often needs to be analyzed and managed by segment. A single RevCent account may contain multiple brands, stores, campaigns, checkout flows, teams, or business units. Campaigns give that activity a clear organizing key. --- ## Where Campaigns Fit in RevCent Campaigns sit near the top of the RevCent data model. A Campaign can be connected to many types of activity, including: ```text Campaign ↓ Sales Customers Transactions Product Sales Shipping Taxes Discounts Subscriptions Subscription Renewals Trials Chargebacks Fraud Detections Pending Refunds Reports AI Assistant filters Organization visibility rules ``` A Campaign should be treated as business context, not just an optional label. When RevCent users or AI workflows work with downstream records, the Campaign often helps explain which part of the business the record belongs to. --- ## Campaigns and Sales Campaigns are closely tied to Sales. When a Sale is created, the Campaign context identifies the business segment that sale belongs to. The Campaign then helps organize the records spawned from that sale, such as product sales, transactions, taxes, shipping, subscriptions, trials, discounts, chargebacks, refunds, and fraud detections. This matters because many business questions are Campaign-specific: ```text How much revenue did this Campaign generate? Which Campaign has the most declined transactions? Which Campaign has the highest chargeback rate? Which Campaign has the most refunds? Which Campaign's subscriptions are performing best? Which Campaign should this support user be allowed to view? ``` For AI and MCP workflows, Campaign context should be preserved when creating or reviewing sale-related activity. --- ## Campaigns and Customers Campaigns are also important for Customer context. A Customer may be created during a purchase attempt, through the API, manually, or as part of another commerce flow. The Campaign helps place that customer into the correct business context. For multi-brand or multi-store accounts, this matters because the same account may contain customers from different storefronts, funnels, or business units. Campaign context can help with: - customer segmentation - customer support visibility - customer reporting - customer-level AI analysis - campaign-specific retention workflows - campaign-specific payment recovery workflows - Organization-based access boundaries A Customer record is an item. A Campaign is the feature used to organize and filter Customer-related activity. --- ## Relationship to Organizations Campaigns and Organizations are related, but they are not the same thing. A Campaign organizes commerce data. An Organization groups users and associated entities, and can be used to restrict visibility for lower-level users. Conceptually: ```text Campaign = organizes Sales, Customers, and related commerce records Organization = groups users and controls what lower-level users can see or access ``` A Campaign can optionally be associated with an Organization. When Campaigns are associated with an Organization, that association can help restrict which Sales, Customers, and related records users in that Organization can view. This is especially important for Supervisor and Employee users. --- ## Relationship to Users Campaigns can affect what certain RevCent users can see when those users are managed through Organizations. RevCent user types include higher-level users, such as account owners and administrators, and lower-level users, such as supervisors and employees. Lower-level users can be assigned to Organizations, and Organization configuration can determine which Campaign-related data they can view. The important operational idea is: ```text Organization has associated Campaigns ↓ Supervisor / Employee users belong to that Organization ↓ Those users may be restricted to Sales, Customers, and related records for those Campaigns ``` This makes Campaign design important for both reporting and access control. A poorly named or incorrectly associated Campaign can confuse users or expose/hide the wrong business activity. --- ## Campaigns vs Organizations | Concept | Main Purpose | Typical Use | |---|---|---| | Campaign | Organize sales, customers, and commerce data. | Segment records by brand, store, funnel, or business line. | | Organization | Organize users and access boundaries. | Group supervisors/employees and restrict visibility. | A Campaign should answer: "What business activity does this record belong to?" An Organization should answer: "Which users or teams should be grouped together, and what should they be able to see or do?" The two can work together, but they should not be treated as interchangeable. --- ## Campaign Visibility Boundaries When a Campaign is associated with an Organization, it can become part of a visibility boundary. This matters when a business has multiple internal teams or operating units. For example: ```text Organization: Brand A Support Team Associated Campaign: Brand A Main Campaign Users: Brand A support employees Result: Users should work only with Brand A Sales/Customers/related records ``` Campaign visibility boundaries are high-impact because they affect what lower-level users may be able to see. AI/MCP should treat Organization association as a meaningful access-control decision, not a cosmetic field. --- ## Campaign Naming Guidance Campaign names should be clear, durable, and business-specific. Good Campaign names: ```text Acme Skincare Main Campaign AcmeSkincare.com WooCommerce Campaign Brand A Subscription Funnel Campaign Brand B Retail Store Campaign Acme Wholesale Campaign ``` Weak Campaign names: ```text Main Default Campaign Store Test Campaign 1 ``` Clear Campaign names help humans and AI/MCP identify the correct Campaign later. This becomes important when creating sales, configuring AI Assistant filters, assigning Organizations, reviewing reports, and troubleshooting customer or payment activity. --- ## Creating and Editing Campaigns In the RevCent web app, Campaigns can be viewed under the Campaign management area. A user can create a new Campaign or edit an existing Campaign. Common Campaign fields include: | Field | Purpose | |---|---| | Name | Human-readable Campaign name. Required. | | Description | Optional explanation of what the Campaign is for. | | Status | Whether the Campaign is enabled or disabled. | | Organization | Optional Organization association. | Because Campaigns can affect sales/customer organization, reporting, AI filtering, and user visibility, Campaign changes should be handled carefully. Before creating a Campaign, it is usually best to check whether a similar Campaign already exists. Duplicate Campaigns with similar names can create reporting confusion and make AI/MCP selection less reliable. --- ## Enabled and Disabled Campaigns Campaigns can have an enabled status. An enabled Campaign is available for active use. A disabled Campaign should generally not be used for new sales or new setup unless the user explicitly intends to use that disabled Campaign. Disabling a Campaign can affect: - new sales workflows - shop or checkout setup - user understanding - reporting filters - AI Assistant filters - Organization visibility expectations AI/MCP should not disable or reactivate a Campaign without explicit user intent. --- ## Campaigns and AI Assistants Campaigns are useful in AI Assistant workflows because they help limit automation to the correct business segment. For account-event triggered AI Assistants, Campaign filters can prevent an assistant from running on the wrong activity. Example: ```text AI Assistant trigger: sale.created.failed.declined Campaign filter: Acme Skincare Main Campaign ``` This pattern is useful when a RevCent account has multiple stores, brands, or funnels and each one needs different AI behavior. Campaign-filtered AI Assistants can support workflows such as: - declined-sale analysis for one Campaign - subscription renewal monitoring for one Campaign - refund-risk alerts for one Campaign - chargeback-threat analysis for one Campaign - fraud review for one Campaign - campaign-specific support escalation - campaign-specific payment recovery Campaign filters reduce noise, cost, and unintended automation. --- ## Campaigns and Payment Workflows Campaigns are not payment processors, gateways, or payment routing rules by themselves. However, Campaign context matters in payment workflows because transactions, salvage transactions, refunds, chargebacks, and related payment records are often interpreted through the sale or customer context that includes Campaign information. Campaigns can help answer payment questions such as: ```text Which Campaign has the highest decline rate? Which Campaign is producing the most salvage transactions? Which Campaign has the highest chargeback rate? Which Campaign has the best gateway approval performance? Which Campaign should a payment recovery assistant monitor? ``` Campaigns are therefore important for payment analysis, even though Payment Profiles and Gateways handle payment routing and transaction processing. --- ## Campaigns and Reporting Campaigns are one of the most important reporting dimensions in RevCent. They can be used to segment and compare business activity across: - sales - revenue - refunds - chargebacks - fraud detections - customers - transactions - subscriptions - renewals - trials - shipping - products - AI Assistant activity - payment recovery - team visibility For simple record lookup, API/MCP list and get operations may be enough. For counts, aggregations, trends, dashboards, revenue summaries, or cross-table analysis, BigQuery is the better tool. --- ## BigQuery Support Campaigns have a dedicated BigQuery table: ```text revcent.user.campaign ``` The `campaign` table contains Campaign records created by the user and can be used in reporting or joined conceptually with other Campaign-linked tables. Known Campaign table fields include: | Field | Meaning | |---|---| | `created_at` | Timestamp when the Campaign was created. | | `id` | Campaign ID. | | `name` | Campaign name set by the user. | | `description` | Campaign description set by the user. | | `enabled` | Whether the Campaign is currently enabled. | Because many commerce tables include Campaign context directly, Campaign reporting often uses the `campaign` table together with operational tables such as `sale`, `transaction`, `customer`, `fraud_detection`, `chargeback`, `salvage_transaction`, `subscription`, or `subscription_renewal`. AI/MCP should inspect the current BigQuery schema before writing production SQL because exact field names can vary by table. --- ## Example BigQuery Questions Campaigns can support questions such as: ```text Which Campaigns are enabled? Which Campaign has the most sales? Which Campaign produced the most gross revenue? Which Campaign has the most declined transactions? Which Campaign has the most chargebacks? Which Campaign has the highest refund volume? Which Campaign generated the most salvage transactions? Which Campaign should a payment recovery workflow prioritize? ``` A simple Campaign lookup can start with: ```sql SELECT id, name, description, enabled, created_at FROM `revcent.user.campaign` ORDER BY created_at DESC ``` For broader metrics, query the relevant operational table and group by Campaign fields available in that table. --- ## Campaigns and Onboarding Campaigns are often created early during onboarding because many later workflows need Campaign context. A good onboarding sequence is: ```text Identify the business, store, brand, or funnel ↓ Create or identify the Campaign ↓ Create or identify Organization if lower-level users need restricted visibility ↓ Connect Campaign to Organization when visibility boundaries are needed ↓ Use Campaign consistently in sales, shop, customer, payment, AI, and reporting workflows ``` For a WooCommerce store, custom checkout, or API-based sales integration, Campaign selection should happen before live sales begin. This prevents sales and customers from being created under the wrong Campaign. --- ## Campaigns in Multi-Business Accounts Campaigns become especially important when one RevCent account supports multiple businesses, brands, stores, websites, or funnels. In a multi-business setup, each major business area should generally have a clearly named Campaign. Examples: ```text Brand A Main Campaign Brand A Subscription Campaign Brand B WooCommerce Campaign Brand C Wholesale Campaign ``` This supports clean reporting and cleaner access control. It also gives AI/MCP a reliable way to choose the right context when the user says things like: ```text Show me sales for Brand A. Create an assistant for Brand B renewals. Restrict this employee to the wholesale business. Run payment performance for the subscription funnel. ``` --- ## Campaign Selection Guidance for AI/MCP When AI/MCP needs to use a Campaign, it should resolve Campaign context carefully. Good selection workflow: ```text 1. Identify the business/store/brand/funnel involved. 2. Check existing Campaigns if the Campaign ID is unknown. 3. Prefer an exact name or ID match. 4. If there is one clear match, use it. 5. If multiple Campaigns could match, ask the user or stop safely. 6. Do not create a duplicate Campaign unless a new Campaign is clearly needed. 7. Verify enabled status before using a Campaign in an active workflow. ``` Do not guess between similarly named Campaigns. Campaign selection affects sales context, reporting, AI automation, and possibly lower-level user visibility. --- ## Common Mistakes Common Campaign mistakes include: - creating duplicate Campaigns with similar names - using vague names such as `Main` or `Default` - confusing Campaigns with Organizations - associating Campaigns with Organizations casually - disabling a live Campaign without confirming impact - using a disabled Campaign for new sales - forgetting to apply Campaign filters to business-specific AI Assistants - running reports without segmenting by Campaign - assuming Third-Party Shop visibility is the same as Campaign-based Sales/Customer visibility - guessing a Campaign when multiple plausible Campaigns exist --- ## Summary Campaigns are a core RevCent feature for organizing sales, customers, and related commerce activity. They are used for segmentation, filtering, reporting, AI Assistant event targeting, and Organization/User visibility boundaries. The most important idea is: ```text Campaigns organize business activity. Organizations organize users and visibility. Users may see different Campaign-related data depending on Organization configuration. ``` Campaigns should be named clearly, selected carefully, and used consistently across sales, customer management, payment analysis, AI workflows, reporting, onboarding, and user access design. --- Document Parent Directory * [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.