Automated Amperity Identity Resolution Digest
Every morning, WebRun opens Amperity, checks the status of the overnight identity resolution run and every source ingestion job, posts a digest of match rates and job status to Slack, and sends an extra Telegram ping if any ingestion job actually failed.
How do I get a daily Amperity identity resolution status check?
WebRun checks Amperity's overnight identity resolution run and every source ingestion job each morning, posts a digest of match rate and job status to Slack, and escalates any actual failed job to Telegram. Retail and CDP teams catch a broken ingestion job before customer profiles fall out of sync across channels.
- A broken ingestion job is caught the same morning, not weeks later
- Match rate trend is visible daily, not just on request
- Only real job failures reach Telegram, keeping it meaningful
Built for retail data teams · CDP administrators · customer data teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
amperity.comin a real browser with your saved login - no setup, no API keys. -
1
Amperity - check resolution and ingestion status
- Open Amperity and check the overnight identity resolution run
- Read the match rate and record counts processed
- Check every source ingestion job's status
Done when Today's resolution run and every ingestion job's status is checked.
-
2
Slack - post the digest
slack.com
WebRun opens Slack to post the digest. - Open the CDP channel in Slack
- Post the match rate and each ingestion job's status
- Note any change in match rate from the prior run
Done when Today's digest is posted in Slack.
-
3
Telegram - escalate any failed job
telegram.org
WebRun opens Telegram to escalate any failed job. - If any ingestion job actually failed, prepare a short escalation
- Send it to the on-call Telegram group
- Name the source and the error
Done when Any failed ingestion job has been escalated on Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun rerun a failed ingestion job?
No. It only reads job status and the resolution match rate. Rerunning an ingestion job stays a manual step for the data team.
Will a normal drop in match rate trigger an alert?
No. Only an actual failed ingestion job escalates to Telegram. Match rate is reported plainly in the Slack digest either way.
Does it see individual customer profiles?
No. It only reads aggregate match rate and job status, not individual identity records.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.