Skip to content

Commit ba6f161

Browse files
committed
campaigns intro doc
1 parent 06b0d19 commit ba6f161

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

docs/campaigns/index.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -59,17 +59,23 @@ A campaign funnel guides customers through a series of pages, each backed by the
5959

6060
```mermaid
6161
graph LR
62-
A[Presale] --> B[Landing] --> C[Checkout] --> D[Upsell 1] --> E[Upsell 2] --> F[Receipt]
62+
A[Landing] --> C[Checkout] --> D[Upsell 1] --> E[Upsell 2] --> F[Receipt]
6363
```
6464

65-
- **Presale** — Marketing page that drives traffic to the campaign
66-
- **Landing** — Customer selects a package
67-
- **Checkout** — Customer enters shipping, billing, and payment details
65+
- **Landing** — Marketing page that drives traffic to the campaign
66+
- **Checkout** — Customer selects package, enters shipping, billing, and payment details
6867
- **Upsells** — Post-purchase offers to increase order value
6968
- **Receipt** — Order confirmation with details
7069

7170
Session tracking is available to monitor performance across all these steps — page views, cart creation, orders, and upsells all flow into real-time campaign performance reports.
7271

72+
:::info
73+
74+
This is a simplified example of a campaign flow. You can customize the flow to meet your specific needs.
75+
76+
:::
77+
78+
7379
### How It All Fits Together
7480

7581
Each campaign is an isolated sales channel with its own packages, offers, and checkout flow. Traffic sources drive customers into campaign funnels, and all resulting orders flow into the merchant's Next Commerce store.

0 commit comments

Comments
 (0)