Weekly Bitly link performance digest posted to Slack

Every Monday at 9am, review how our Bitly links performed over the past week and post a written digest to our marketing channel in Slack. Use a cron trigger for this. Bitly webhooks require a paid or enterprise plan and return 403 otherwise, so the workflow should list the links and fetch their stats itself on each run rather than waiting to be notified.

Start by resolving which Bitly group to report on. The connected user record exposes a default_group_guid, and that is the group to use unless I specify another one. Then call Bitly's "Retrieve Bitlinks by Group" to pull the links in that group, and narrow the set to links that have been active in the last 30 days so old and abandoned links do not clutter the report.

For each of those links, call Bitly's "Get a Clicks Summary for a Bitlink" twice so you can compare week over week. Bitly's metric endpoints accept a unit (minute, hour, day, week, month) along with units and unit_reference to define the window, so request one summary covering the last 7 days and a second summary covering the 7 days immediately before that. The difference between those two numbers is the movement I care about. Note that Bitly rate limits per endpoint and returns 429 when exceeded, so pace these calls and keep going rather than failing the whole run if one link errors out.

Once you know which links actually performed, enrich only the top performers. For those, call Bitly's "Get Metrics for a Bitlink by Referrers" and "Get Metrics for a Bitlink by Country" over the same 7 day window, so the digest can say where the traffic genuinely came from instead of just how much of it there was. Do not enrich every link, only the ones worth commenting on.

Group the links by their Bitly tags and summarize each tag as a campaign unit rather than reporting a flat list of raw URLs. For each campaign give the combined click total, the week over week change, and the individual links inside it. If some links carry no tags, report them together under a single untagged group instead of dropping them.

Write the digest so it leads with the three best performing links across all campaigns, each with its click count and its week over week change. After that, cover each campaign in turn. Explicitly flag any link whose clicks dropped by more than half compared to the previous week, and put those in a clearly marked section so they do not get lost. For each campaign, add one sentence explaining where the traffic actually came from, drawing on the referrer and country breakdowns. Use judgement here: rank the links, decide which movements are worth calling out, and write it as a short narrative a marketer can read in under a minute, not as a raw data dump.

Send the finished digest to our marketing channel using the Slack Bot integration's "Send a Message" operation. Format it for Slack readability with a clear heading, short sections, and the links rendered so they are clickable. If there was no click activity at all in the past week, still post a brief note saying it was a quiet week, so the team knows the report ran.