Talk through your traffic-quality workflow.

What to share

Describe your advertising channels, providers, websites, account and client structure, monthly traffic range, conversion or lead model, current tracking, investigation process, team roles, privacy requirements, reporting needs, and the decision you want the platform to support.

Do not send passwords, API keys, payment data, raw session recordings, unnecessary personal information, unrestricted exports, or live customer secrets. A first conversation should use the minimum information needed to understand fit.

• Providers and approximate operating scope
• Websites, clients, users, and roles
• Current measurement or investigation problem
• Required integrations, privacy, security, and service boundary

What the review can and cannot do

The review can map your needs to current product foundations, beta interfaces, plan allowances, integration readiness, external dependencies, and product work still required. It can identify the next evidence or owner needed for a responsible decision.

A contact request does not create a subscription, payment, provider authorization, installation, service level, support commitment, security approval, legal conclusion, detection result, blocked click, provider credit, savings, conversion, revenue, or ROI outcome.

Information to avoid

Do not include passwords, secret keys, access tokens, full payment card data, government identifiers, raw credentials, unrestricted customer exports, unmasked recordings, or sensitive personal information in an initial request.

If a later investigation genuinely needs sensitive evidence, the responsible owner should confirm the purpose, scope, transfer method, access, retention, recipients, and deletion path before it is shared.

Current submission boundary

The public contact experience is a structured preparation and routing page. A production contact form, mailbox, CRM connection, spam protection, retention rule, response commitment, and privacy notice must be activated and tested before the site claims that a message has been transmitted or received.

Until that activation evidence exists, the page does not display a decorative form or success state that could mislead a visitor into believing a request was delivered.