> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/technical-guides/front-end-integration/acquisition-mode.md).

# Acquisition mode

Smartico can interact with anonymous users by sending pop-ups, Push notifications, and displaying mini-games.

This is called '**Acquisition mode**' and is mainly used on the landing pages at the stage when the user hasn't registered yet.

From a setup perspective, '**Acquisition mode**' requires a separate label on the Smartico side; this way, real and anonymous users are fully separated, and the operator can build an independent setup for anonymous users.

### Provisioning and Activation

Acquisition labels are dedicated label instances in Smartico (label mode: Acquisition) with the Acquisition product enabled. Because they require separate infrastructure configuration, an acquisition label must be requested through your Smartico Customer Success Manager (CSM) or Smartico Support. Once provisioned, you will receive dedicated label and brand API keys specific to your acquisition environment.

## Technical setup

1. Load the Smartico script on the landing page.

On the front-end of the landing pages, set the Smartico script in the following way

<pre class="language-javascript"><code class="lang-javascript">&#x3C;script>
(function(d, r, b, h, s){h=d.getElementsByTagName('head')[0];s = d.createElement('script');s.onload=b;s.src=r;h.appendChild(s);})
(document, 'https://libs.smartico.ai/smartico.js', function() {
<strong>    _smartico.init(
</strong><strong>        '_label_key_for_acquisition_label_', 
</strong><strong>        { 
</strong><strong>            brand_key: '_brand_key_for_acquisition_',
</strong><strong>            generate_visit: true
</strong><strong>        });
</strong>});
&#x3C;/script>
</code></pre>

Be sure to use the acquisition label and brand keys, not those used for registered users!

2. Set the current language of the landing page

```javascript
<script>
    window._smartico_language = 'fr';
</script>
```

3. Support different domains for landing pages.

In case the landing page is hosted on a domain that is different from the main domain of the site

* Setup libraries that are needed for push notifications in the same way as explained in Step 3 of [Front-end integration guide](https://help.smartico.ai/welcome/technical-guides/front-end-integration/pages/fZuSGL9QlAW3KpaOsRDy#3.-preparation-for-web-push-notifications)
* For detailed service worker setup and push assets, see the [Push configurations](/welcome/technical-guides/front-end-integration/push-configurations.md) guide.
* When the user is redirected from the landing page to the main site, pass in the URL the ID of the visitor from the landing page using the following code

```javascript
var v = window._smartico_visitor_id || window.localStorage.getItem('_smartico_generated_visitor_id');
window.location.href = 'index.html#_smartico_visitor_id=' + v;
```

## What is possible to do in the Acquisition mode

1. You can request permissions for push notifications using Smatico campaigns with deep links or just by calling JavaScript: \_smartico.requestPushPermissions()
2. You can send Popups and run Mini-games
3. You can do basic segmentation by:
   1. Country
   2. Browser type
   3. Push permissions status

### Feature Capabilities and Limitations

* **Supported Channels:** Web Popups, Web Push Notifications, and standalone mini-game widgets.
* **Segmentation & Triggers:** Country (GEO), Browser/Device, Push permission status, UTM parameters (`utm_source`, `utm_medium`, `utm_campaign`), and custom client events sent via `_smartico.event()` or `_smartico.action()`.
* **Mini-Game Prize Limitation:** Mini-games run on an acquisition label **do not** transfer won prizes to a player's real account after registration on the retention label. If you need anonymous visitors to play mini-games and automatically claim their prizes upon registration, use [Visitor mode](/welcome/technical-guides/front-end-integration/visitor-mode.md) on your main retention label instead.
* **No Gamification Widget:** Standard gamification widgets (levels, missions bar, shop, leaderboards) are not supported in Acquisition mode.
* **Mutual Exclusivity:** Acquisition mode and Visitor mode cannot be run simultaneously in the same script instance.

{% hint style="info" %}
Note: if your main goal is to run mini-games on the landing page and you **don't** plan to use Popups and Push notifications, there is a simplified setup that you can find in [this guide](/welcome/products/mini-games/mini-games-on-the-landing-pages.md)
{% endhint %}

## Frequently Asked Questions

**What is the difference between Acquisition Mode and Visitor Mode?**

Acquisition Mode uses a separate dedicated label to create anonymous visitor profiles, enabling popups, push notifications, and acquisition campaigns for unregistered traffic, but without prize carryover for mini-games. Visitor Mode runs directly on your main retention label using a proxy test user, allowing read-only gamification displays and mini-games with prize conversion upon registration, but without popup campaigns for anonymous visitors.

**Can a player claim prizes won in Acquisition Mode after registering?**

No. Because the acquisition label is isolated from the main retention label, prizes won on an acquisition landing page cannot be automatically credited upon registration. To award prizes on registration, implement [Visitor mode](/welcome/technical-guides/front-end-integration/visitor-mode.md) on your retention label.

**How does cross-domain visitor tracking connect an anonymous visitor to their registered account?**

When a user clicks from the landing page to your main site, passing `_smartico_visitor_id` in the URL query string or hash allows the SDK on the main site to store the visitor ID in the browser. When the player subsequently registers and logs in, the SDK passes this visitor ID to associate their prior anonymous visit with their registered account profile.

**Can I use both Acquisition Mode and Visitor Mode together?**

No. Acquisition Mode and Visitor Mode are separate modes designed for different architectures and cannot be initialized together in the same session.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/technical-guides/front-end-integration/acquisition-mode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.