INTO THE LION’S DEN / PRIDE

Promotion & community evidence

Choose what to promote. See what people use. Record the community outcomes you can substantiate.

Site tracking uses Pride’s existing GA4 destination. The nine podcast reporting fields and branded-site comparison are configured in Pride’s GA4 property; page views, watch clicks, playback starts and campaign labels were verified in GA4 Realtime on October 26, 2026. Analytics and community records now live in the signed-in Pride workspace, shared with your approved dashboards.

Give every placement a clear source

Use these links in external promotions. Ordinary links between Pride pages keep their original attribution.

Campaign tags use lowercase labels. A QR visit records an observed visit, not an exact scan or a unique person. Do not put personal details in campaign labels.

Review the shared analytics source

Your private Pride master dashboard now owns the shared podcast data. Open the permanent workspace to see source status and the latest saved reporting period.

Open private analytics workspace ↗

Sign-in is required. The same approved Pride summary is read by the Pride master dashboard and SPIKE. No private measurements are copied onto this public page.

Save community evidence once

Community records now save to the private Pride source with revision history, review status and linked evidence. They are available after closing your browser and on your other signed-in devices.

Open permanent evidence workspace ↗

Use the same record ID when editing an outcome. Review the supporting source before marking it verified. Saving a record does not publish a public impact claim.

Earn attention. Document the benefit.

Before promotion: confirm names, local relevance, permissions and source facts. Each piece should teach, entertain, earn trust, invite sharing or be worth saving; aim for at least two.
Give the audience a useful next step: a relevant conversation, a chapter, a guest’s work, or an invitation to contribute.
Tag and test: one placement per campaign link. Check the mobile destination and consented GA4 receipt before distributing.
Review weekly: identify which placements earn starts, sustained listening and guest exploration. Use the first four complete weeks as a baseline before setting performance targets.
Build the proof monthly: review unique, sourced community outcomes by city and Pride standard. Publish only supported, permission-cleared results. Do not turn traffic into claims of local leadership.

Primary measures: observed playback starts, 60-second listening signals, and unique verified community outcomes. Guardrails: accurate claims, appropriate consent, and a useful mobile experience.