# Setup wizard

The setup wizard reads the last 30 days of a website's data and its current settings, then proposes which events, conversions and funnel to switch on. It checks each proposal against the website's own data, shows every change before anything is saved, and can be undone.

## What it does

Most conversion-report problems start in the setup: an event that was never created, a purchase counted twice, a funnel built from the wrong events. The setup wizard decides what a website needs and checks each proposal against that website's data before switching it on.

You reach it from three places: the **Setup wizard** row in **Admin**, the link above the **E-commerce** and **Funnel** reports, and the link in the Admin **Events** panel. Its address is `/setup-wizard`.

## Steps

1. Press **Start**. If the website has more than one web data stream, pick the stream first.
2. The wizard reads the current settings and the last 30 days of data. This usually takes less than a minute.
3. Answer **A few questions**, for example the kind of website (online shop, lead generation, software or membership, or hosting with WHMCS), the page people see after sending a form (or, when there is no such page, which form counts), or which contact links should count as a contact. That question lists the messenger links people click (WhatsApp, Telegram, Bale, Eitaa, Rubika, Instagram direct, Messenger); any other link sits under **Other links people click**, closed and unticked. Links to social profiles, app stores, trust seals, maps, payment pages and the website's own addresses are never offered. Answers the wizard worked out by itself, and your own, are listed under **Your answers**; press **Change** to correct one.
4. In **Review**, look at each change and tick or untick it.
5. Press apply. The changes start counting about a minute later.

## Review

Each line is one change, with its event source and evidence next to it:

| Label | Meaning |
| --- | --- |
| **Working** | The event already works and is left alone. |
| **Ready** | Checked against the website's data and ready to apply. A ready line may still start unticked, for example on a website with several data streams; tick it to apply it. |
| **Not proven** | Not proven by this website's data yet, so it is not switched on. |
| **Blocked** | Can't be set up yet; the reason and what to do are shown next to it. |
| **Note** | Kept as it is, with a caution next to it, for example purchases that have no order number; their conversion and funnel step then start unticked. |
| **On hold** | Waits for an option to be switched on, for example outbound click measurement or the Google Tag Manager line, or for a feature not added yet, such as lead values. |

Notes above the list point out problems the wizard found but can't fix itself, such as an event that is counted twice or an answer it could not use.

Changes the wizard may propose:

- Create an event with an event rule, for example `contact_click` for clicks on WhatsApp or Telegram links, or `generate_lead` for a form's thank-you page.
- Pause a duplicate rule that creates the same event twice (never deleted).
- Mark an event as a conversion. You can already enter a value for a lead conversion, but its line is shown **On hold** and not applied yet: values are not added to leads for now. If you press **Apply** right after typing a value, nothing is applied the first time, so you see that line; press **Apply** again to apply the rest. A lead value is never counted as revenue; revenue comes from purchases only.
- Switch on outbound click measurement or form measurement when a proposed event needs it.
- Read e-commerce events from Google Tag Manager. The line says which events start or stop being read and whether purchases come from Google Tag Manager or from your server. A line such as **Count sign_up from Google Tag Manager** works only together with this line; unticking it plans those events another way. When the wizard has seen an event name but not yet enough of it, the line reads **Test reading events from Google Tag Manager**: nothing is counted, a small script records what Google Tag Manager sends, and a later run proposes counting it.
- Set the funnel steps.

A product view created from a page address (an event rule on your product pages) counts that a product page was opened, but it carries no product name and no price, so the product reports stay empty for it; a note above the list says so. Product names, prices and order values come from your shop's plugin, your server or Google Tag Manager e-commerce events.

**Its trigger was seen … times in the last 30 days** is how often the page view, link click or form send the rule watches appeared in the website's past data. A rule that counts once per visit or once per person will count fewer events than that. When a proposal counts a form only because it was sent, it is unticked by default, because a sent form is not always a successful one. The conversion, value and funnel step built on that event start unticked too; ticking one of them also ticks the event rule it needs, and unticking the rule unticks them again. A rule left unticked for another reason (its page is already another step's, or its source stopped) is not ticked for you: tick the rule first. A change is never applied without the change that creates its event. On a line that keeps a working source, **Seen … times** counts only since that source's setup last changed, so it can cover fewer days (see below).

A thank-you or welcome page where many visits start (bookmarks, links shared in messengers) is proposed unticked, because not every view of it is a real lead or sign-up. An address is one page however it is written: with capital or small letters (`/Thank-You` or `/thank-you`, `%D8` or `%d8` in its Persian part), with an Arabic-keyboard ك or ي for the Persian ک or ی, with or without the last slash, and with a doubled slash (`//thank-you/`). A page told apart only by its query, such as `/?page_id=15` or `/contact/?sent=1`, is its own page, and the rule for `/contact/` never counts `/contact/?sent=1`; tracking parts such as `utm_source`, `gclid` or `gad_source`, and language parts such as `lang=fa`, never are; a page with both `page_id` and `sent` is one page whatever their order or letter case, and a form's own success flag such as `?status=success`, `?message=sent`, `?mailsent=1`, `?step=done`, `?verified=1`, `?welcome=1`, Shopify's `?contact_posted=true` or a bare `?success` makes a page of its own too, and so does Joomla's `layout=complete` (its registration done page). On the home page, an address such as `/?route=checkout/cart` (OpenCart and similar shops) is its own page, and WooCommerce product pages without pretty addresses (`/?product=hoodie`) are one product page together. On a site that changes pages after a `#` (`/#/signup/complete`), the page is read the same with or without a query before the `#`, with or without a last slash, and with or without the route's own query (`#/checkout?step=2`), except a form's success flag (`#/contact?sent=1` is the form's own done page). Such a page is counted only when it opens as a full page, for example a return from the payment page or a shared link: moving between pages inside the open app sends no page view, and a note in the Review says so; any other part after a `#`, such as `#top`, never makes a page of its own when a query stands before it. A page whose address carries a number, such as `thanks.php?id=1001`, is one page for every number, and so are pages that differ only by a request number inside the address (`/quote/8801/thank-you/`). On a WooCommerce shop without pretty addresses, the order-received page (`/?page_id=8&order-received=…`) is never read as the checkout page. On a website in two languages, a page that exists under both (`/fa/thank-you/` and `/en/thank-you/`, or `/thank-you/` and `/en/thank-you/` when one language has no prefix) is also offered as one page for both languages. A folder's page and its index file (`/thank-you/` and `/thank-you/index.html`) are one page. The home page, a language's home page (`/fa/`) and `/index.php` are never proposed as a goal's page. A word that marks a page as another goal, such as order or payment, is read only as a whole word, so a service page such as `/invoice-factoring/thank-you/` can still be a lead form's thank-you page. A product named after such a word (`/product/golf-cart/`) never keeps its product group out. A careers, unsubscribe, survey, login or password page is never proposed as a lead page, a password page never as a sign-up page, a cart, checkout or order page never as a product page, a login page never as the cart or the checkout, and a checkout address that says the order is done (`?step=done`, `?result=ok`) never as the checkout. On a lead-generation website, a registration's thank-you page (a webinar sign-up) can be the lead page. A thank-you page where most visits start is not used, even when you pick it yourself, because its rule would count bookmarks and shared links as leads; a cart or checkout page where most visits start is not used either; the same holds for a page a form hosted elsewhere (Porsline, Google Forms) sends its visitors to. If you are sure, add a rule for it yourself in Admin › Events. Each goal is counted from one page; when other pages look like the same goal (a second form's own thank-you page, a page in another language under another address, Shopify's `/collections/…/products/…`), a note says how many views the chosen page leaves out, so you can add a rule for them in Admin › Events. When a shop, a WHMCS website or a software or membership website has a thank-you page, the wizard also asks whether it is a lead form's page; it never decides that by itself, because the page may be the order page. A Shopify checkout on your own domain (`/checkouts/…`) has a separate address for every visitor, so the wizard can't set a rule for it and doesn't propose one. On a website whose pages span several hosts (for example `app.example.com` beside `example.com`, or `m.example.com`), a page that exists on more than one is offered both for each host and for every host together. When the same page is chosen for two goals (the cart page as the checkout page too), the second one's rule is proposed unticked, because one visit would count as both. When your server or plugin has sent an event only a few times, it stays the source, but its conversion and funnel step start unticked. When it stopped sending an event days ago while the website has sent it several times since (for example a plugin that was removed), the wizard plans the event as if the plugin were not there and says so. When the website itself sent an event only a few times (often a test), those events are left alone, and the page rule for it, its conversion and its funnel step are proposed unticked.

> **One source per action**
>
> The wizard aims for one source per event. Your server or plugin comes first; then Google Tag Manager, when it is already set to send the event; then an event rule you already have; then the website's own code. It only changes what it can be sure of: when the data can't tell which of two sources sends an event, it leaves both as they are and warns you. A purchase rule made from a page address is paused once your server or plugin sends orders regularly; until then both are kept and a note warns you. A source that already works is never replaced.

Two cases get a note instead of a decision. Right after something changed (a rule was made, edited or switched off, Google Tag Manager reading was switched on or off, or your server or plugin started sending an event), the wizard only counts what happened since that change; with just a few days of data it says so and asks you to run it again later. And on a website with more than one data stream, events are stored for the whole website, so the wizard can't always tell which data stream sends an event: a line that says an event already works may be about another data stream. Check each pause line before you apply. A new rule for a page or a contact link counts only the visits of the data stream you picked, so on such a website it is proposed unticked: tick it when that page belongs to this data stream's site.

When you open the wizard again, the review is rebuilt on the website's current settings; if that fails, a note says the review may be out of date. **Run again** asks before it replaces an open review. If the website's settings change between the review and the apply, nothing is applied; the plan is rebuilt on the new state so you can review it again. If a rule or the Google Tag Manager setting changed after the wizard read the data, the plan says so and **Apply** stays off until you press **Scan again**: the old reading may count a source that has since stopped. A reading more than a day old needs **Scan again** too.

A rule that exists but has not fired yet reads **… has a rule, but it has not fired yet**: the wizard leaves it as it is. A rule that reads clicks or form sends while that measurement is off reads **… has a rule, but it can't fire while … is off**, with a line to switch the measurement on. When another conversion you already count fires on the same page as a goal (for example your own `order_complete` on the WHMCS order-complete page beside the module's purchases), a note says one action may be counted as two conversions. When outbound click measurement is off, the wizard proposes switching it on so contact links can be counted; when it is on and no click on a contact link was seen in the last 30 days, the contact-click proposal is blocked. It is blocked too when you choose more link domains than one rule can hold; choose fewer.

## Is it working?

After applying, the **Is it working?** card shows, for each new event rule and conversion, how many events real visitors have sent since the setup was applied. Test traffic is not counted. Events are counted for the whole website, not per data stream. **No events yet** is normal in the first hours; if it still says so the next day, check the page or link again.

## Undo

**Undo the setup** puts every change of the last run back as it was. Only the most recent run can be undone, and anything changed by hand since then is left as it is.

## Frequently asked questions

### Does running the wizard change anything without asking me?

No. Nothing is saved until you press apply in the **Review** step, and only the ticked changes are applied.

### Why was no purchase event proposed?

A purchase without an order number can't be trusted; reloading the thank-you page counts one order several times. The wizard sets up purchases only from a source that carries the order number, such as the WordPress plugin, the WHMCS module or a server-side feed. Without one, the purchase is shown as **Blocked** with the reason.

### What happens to event rules I already made?

They are never deleted. When a rule creates an event that your server, plugin or Google Tag Manager already sends, or two rules create the same event the same way, the wizard proposes pausing the extra rule so the event is not counted twice. A rule that matched nothing in the last 30 days is paused when something else already sends its event, or together with the change that replaces it. When the website's own code also sends the event, or the data can't tell which source sends it, the wizard changes nothing and warns you. Undoing the setup switches a paused rule back on.

### What if I change something by hand after applying, and then undo?

Undo restores only what has not been touched since the setup was applied. Anything you changed by hand stays as it is and is counted in the undo message.

### Who can run it?

Editors of the website only. Viewers see a note that only editors can run it.

## Related

- [Create and Modify event rules](https://docs.adpix.io/en/analytics/collect/event-rules/)
- [Key events](https://docs.adpix.io/en/analytics/collect/key-events/)
- [Enhanced measurement](https://docs.adpix.io/en/analytics/collect/enhanced-measurement/)
- [Google Tag Manager and the dataLayer](https://docs.adpix.io/en/analytics/collect/google-tag-manager-datalayer/)
- [The conversion funnel](https://docs.adpix.io/en/analytics/reports/funnel/)

---

[Docs](https://docs.adpix.io/en/analytics/collect/setup-wizard/) · AdPix
