adattributionkit

Verify JWS-signed iOS ad postbacks and deduplicate events.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/DFly7/iOS-FastAPI-Supabase-AI --skill adattributionkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adattributionkit
Source: https://github.com/DFly7/iOS-FastAPI-Supabase-AI/tree/main/.agents/skills/adattributionkit
Command: npx skills add https://github.com/DFly7/iOS-FastAPI-Supabase-AI --skill adattributionkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AdAttributionKit enables ad networks, publishers, and advertisers to measure installs and re-engagements from iOS ads without exposing user-level identifiers or device-level data, reducing privacy risk while preserving actionable conversion metrics.

Core Features & Use Cases

  • Signed impressions and JWS verification: register and validate impressions from ad networks and verify device-sent postbacks server-side to prevent fraud.
  • Conversion windows and values: manage fine and coarse conversion values across multiple time windows and lock postbacks to finalize values early.
  • Re-engagement and migration: support re-engagement flows with conversion tags and coexistence/migration strategies with SKAdNetwork for publishers and advertisers.
  • Use Case: A publisher app registers signed impressions, a server verifies postbacks with Apple public keys and deduplicates by postback-identifier, and the advertised app updates conversion values to trigger timely postbacks.

Quick Start

Use AdAttributionKit to record a signed impression, update the conversion value on first launch, and verify incoming postbacks at your well-known HTTPS endpoint.

Frequently Asked Questions about adattributionkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does iOS ad attribution work without exposing user-level identifiers?

Privacy-preserving iOS ad attribution measures installs and re-engagements by using signed impressions and device-sent postbacks, ensuring actionable conversion metrics without exposing user-level identifiers.

How do I verify JWS signatures for ad attribution postbacks on my server?

You verify JWS signatures for ad attribution postbacks by validating device-sent postbacks server-side against Apple public keys at your HTTPS well-known endpoint, deduplicating events by postback-identifier to prevent fraud.

Can I use AdAttributionKit alongside SKAdNetwork for publisher migration?

Yes, AdAttributionKit supports coexistence and migration strategies with SKAdNetwork, allowing publishers and advertisers to transition while maintaining re-engagement flows and conversion tagging.

How do I update fine and coarse conversion values across multiple time windows?

You update fine and coarse conversion values across multiple time windows by modifying values in the advertised app and locking postbacks to finalize values early and trigger timely postbacks.

What are the limitations of privacy-preserving ad attribution with tiered crowd anonymity?

Privacy-preserving ad attribution with tiered crowd anonymity requires meeting specific privacy thresholds before sending postbacks, which can delay measurement and restrict the granularity of conversion value data.