[appdevelopsk]

Why

The four editorial guides emitted only legacy guide_store_click. As a result, clicks from guide pages could be missing from the site's shared download_click store-outbound funnel, while homepage, catalog and app support pages already emit the common event. This makes acquisition attribution incomplete.

Fix

• For all 17 direct Google Play buttons across four guides, retain exactly one guide_store_click and add one download_click on the same click.

• Standardize the event fields store='google_play', location='guide', placement='guide_card', app_slug, and the allowlisted guide name. Do not send personal data or raw referrer/query strings.

• Do not alter any Play Store links, their UTM/referrer parameters, or the 17 new first-party Features & FAQs links. The new detail links continue emitting only the unified app_detail_click event.

Verification

Direct source checks on all four GitHub branch HTML blobs passed: one legacy store event listener and one common download event per guide, 17 Play links and 17 matching detail links still present.

Added scripts/test_guide_store_events.cjs which executes the actual store-click handler source with Node VM mocks; 8/8 tests passed locally on representative guide HTML, and the test script hash matches GitHub exactly: 2c68a19464b864aed75e8b99a96ffa2476a77935.

README QA command updated. Full deployed-browser/GA4 DebugView attribution not verified. Two distinct GA4 event names on one click are not two installs. GitHub Actions not used; deployment is owner-controlled.