Before Connecting
Identify the account owner, website administrator and person responsible for approving data processing. List the information being sent: catalogue data, public delivery terms, consultant messages, enquiry contacts and visitor events. Secret instructions, passwords and customer documents must not enter materials used to answer shoppers.
Select the store before checking a quota. Websites in the same account can have different capabilities. The loaded account view matters more than an assumption that similar menus imply identical terms.
Where to Check the Plan and Usage
- Open “Plan and balance”.
- In the plan block, check its name, cost, catalogue allowance, dialogues for the period and expiry date.
- Compare uploaded items and used dialogues with that store's own limits.
- Before changing plans, read the warning if the catalogue does not fit the new allowance.
- After payment, verify the updated balance, expiry and relevant section. Creating a payment is not the same as confirmed payment.
| Situation | Meaning | Next Action |
|---|---|---|
| Missing AI switch or consultant section | The capability may not be included | Check the selected store's plan |
| Consultant not connected | Dialogues are not included in current terms | Review an appropriate plan |
| Quota exceeded | The account describes soft limits | Review consumption and expansion terms |
| Plan expired | A separate payment-expiry situation | Check the date and top-up |
| Search in simple mode | Exact word matching remains | Restore the paid mode |
Soft limits do not mean indefinite free service and do not cancel plan expiry. In simple mode, the interface warns that typos, wrong-layout correction, synonyms, semantic search, ranking learning and the consultant are disabled; catalogue data, settings and statistics remain. Read the actual grace period from the current message, not from this article.
Do not assume every plan is unlimited. Check prices, currency, individually agreed terms and current quotas in the account and offer documents. This guide does not establish a universal trial period or availability commitment.
Monthly, Annual and Balance
Plan selection offers monthly and annual modes. The annual option is charged upfront, not as twelve independent payments. Before connecting a plan, review the charge and any insufficient-balance message. Topping up starts payment through the provider; after returning, check confirmation rather than just the redirect to a payment page. Do not confirm a smaller plan while ignoring a warning about items that will stop being found.
Keys and Staff Access
Under “Settings → Integration keys”, the public key is labelled as a widget identifier, not a secret. The Bitrix module requires the selected site's secret Integration key with the ik_ prefix. Separate “Integration tokens” grant search and reindex abilities; they are not a universal substitute for the site's module key. Secrets are shown when issued, so keep them in protected storage, not customer correspondence or screenshots.
Reissuing a key or revoking a token stops old integrations. First list every place using it, then update configurations and verify catalogue upload. Do not revoke the only working token as an experiment to repair search.
Under the account-login section in “Settings”, you can enable an authenticator-app code and confirm setup. Store recovery codes separately: they are shown once. Agree staff access with the account owner; do not share your recovery codes with staff.
Knowledge and Customer Information
Active knowledge-base materials are used for the consultant's answers to shoppers. Upload only information that may be disclosed to visitors. Do not add private or unpublishable information: a restricted source page does not protect its uploaded copy from being used in an answer.
Customers submitting an enquiry must see consent to personal-data processing and a link to the store's policy. data-policy-url helps supply that link, but the attribute alone does not make an integration compliant with every legal requirement.
Cookies and Verification
The integrator can declare window.ANMARTO_CONSENT = 'denied' before the loader and call AnmartoWidget.setConsent(true|false) after the visitor chooses. With refusal, the widget uses a temporary tab identifier and disables client telemetry transmission, query-history requests and behavioural tracking. This limits client mechanisms, not data transmission needed to provide the service: search queries and chat messages are still sent. The flag does not disable server-side search processing or the recording of search statistics. Without the flag, client tracking is enabled: connect the store's banner explicitly to the widget.
Check both visitor choices and inspect the page HTML for accidental secrets. Verify legal grounds, retention periods, conversation access and processing locations against the published policy, contract and responsible specialist rather than inferring them from banner behaviour.
Related articles: account keys, knowledge base, analytics, all articles.