Skip to content
Menu
Home / Workflow

Route website account signals into a CRM review queue

Treat a website signal as context for account review. Preserve whether the match is a company or a person, retain the source event and let routing rules determine the next action.

The short answer

Treat a website signal as context for account review. Preserve whether the match is a company or a person, retain the source event and let routing rules determine the next action.

01Capture the event and permission context02Resolve the account03Remove repeat events04Apply routing rules05Write context for a person to review

1. Capture the event and permission context

Record the event ID, timestamp, page category and identification level. Review the provider’s data-processing terms and your privacy requirements before installing a tag.

2. Resolve the account

Normalize the company domain and find an existing CRM account. Keep a person-level claim separate from an organization match. Do not create a named contact from a company-only event.

3. Remove repeat events

Use the provider event ID as the deduplication key. Aggregate related visits into an account-level summary instead of sending a fresh notification for every page view.

4. Apply routing rules

Route existing customers to their owner and open opportunities to the deal owner. Keep uncertain matches in a review queue. Define which page categories matter to your team before assigning priority.

5. Write context for a person to review

Create an internal task with the account, observed activity and source. The task should explain why the account appeared without claiming that a visit establishes purchase intent.

Questions buyers ask

Should every visitor trigger an outbound message?

No. A visit alone does not establish intent or permission. Review identity quality, existing relationships, routing rules and applicable privacy requirements before a person decides on follow-up.

What should go in the CRM?

Store the account, identification level, source timestamp and a concise activity summary. Keep the original event reference for review and apply your data retention policy.

Keep comparing

Sources and verification

Implementation documentation

n8n webhook documentation · n8n Code node