User Profile

@yw21 did you mean passing the same parameters to SKAdImpression and StoreKit controller including signature? If you pass signature created with “fidelity-type” 0 - most probably it won’t work for StoreKit controller, but StoreKit will record impression and view-through attribution postback may arrive. If you pass all the same parameters except of 2 different signatures: 1) with “fidelity-type” 0 to SKAdImpression and 2) with “fidelity-type” 1 to StoreKit controller - click attribution have higher priority over view-through attribution (according to Apple’s doc). So postback from click attribution should be sent, I assume. Does it make sense? 1) Did someone performed tests already to confirm? 2) Is it ok to pass the same parameters to SKAdImpression and StoreKit controller except of signature? 3) Can / should “nonce” and “timestamp” be different? Thanks in advance!

Hi roofeel! I haven’t tried to use prime256v1 since our key was generated using prime192 elliptic curve, for signature I am using prime192 EC and it still works for SKAdNetwork v2.1 and iOS 14.3. For SKAdNetwork v2.2 and iOS 14.5 beta it doesn’t work, no postbacks, but it seems it’s not related to the key or prime192 vs prime256 so far. Have you checked Console logs from device when you present StoreKit controller, downloading advertised app and opening it? I see the following: default 17:29:24.867316+0200 ProductPageExtension SKAdNetwork - Preparing to add install attribution parameters Source App Adam ID: 31bca02094eb78126a517b206a88c73cfa9ec6f704c7030d18212cace820f025f00bf0ea68dbf3f3a5436ca63b53bf7bf80ad8d5de7d8359d0b7fed9dbc3ab99 Source App Bundle ID: 2f884d30b0b87a0fc88af6cf9a10bc0d9a8a2b9b14be84697ca1bb6ea285a5999eb570af1d8aeca91b014582d5ae230fc1a853b17ded684b5f487778b8ecad6a default 17:29:24.867409+0200 ProductPageExtension Adding install attribution params from bundleID: mysampleappbundle ID adamID: 0 default 17:29:24.867619+0200 appstored [XPCServiceEntitlements]: We have the entitlement: com.apple.itunesstored.private for pid: 1172 result: 1 error 17:29:24.899281+0200 appstored table install_attribution_params has no column named fidelity_type in "INSERT OR REPLACE INTO install_attribution_params (ROWID, campaign_id, ad_network_id, attribution_signature, source_app_adam_id, local_timestamp, version, app_adam_id, timestamp, fidelity_type, impression_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?);" default 17:29:24.899404+0200 appstored [0x1007c6fc0ublic}@] Error: Error Domain=SQLiteErrorDomain Code=1 "table install_attribution_params has no column named fidelity_type" UserInfo={NSLocalizedDescription=table install_attribution_params has no column named fidelity_type}

Hi fmaschmeier! The latest test which I performed couple of days ago on device with iOS 14.3 with SKAdNetwork v2.1, with our p192 private key has succeeded. Postback has arrived as expected. Also I made tests during last week and today on device with iOS 14.5 beta, with SKAdNetwork v2.1 and v2.2 (checked StoreKit and view-through attribution) - there are no postbacks. As I can see from Console logs, for view-through attribution Apple are making version check and “2.2” for some reason is considered “incorrect version”. For StoreKit attribution there is error messages related to “fidelity-type”. Looks like Apple’s bugs or SKAdNetwork 2.2 is still not enabled.

Hi zedwill! No, it is still not clear if we should change or not.

Thank you for your response! I've submitted report: https://feedbackassistant.apple.com/feedback/8796185.