BEGIN:VCALENDAR VERSION:2.0 PRODID:-//AdShift//Ad platform deadlines//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALNAME:AdShift: ad platform deadlines X-WR-CALDESC:Meta\, Google\, TikTok\, Klaviyo and Shopify ad deadlines from adshift.co X-WR-TIMEZONE:America/New_York REFRESH-INTERVAL;VALUE=DURATION:PT12H X-PUBLISHED-TTL:PT12H BEGIN:VEVENT UID:google-ads-api-v22-sunset@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261007 DTEND;VALUE=DATE:20261008 SUMMARY:Google: Google Ads API v22 sunset on Oct 7 DESCRIPTION:Google Ads API v22 sunset on Oct 7\n\nWhat to do: Confirm your reporting connectors and scripts run on v24 or later so the February 2027 v23 sunset doesn't catch you.\n\nSource: https://ads-developers.googleblog .com/2026/09/google-ads-api-v22-sunset-reminder.html\nDetails: https://ads hift.co/changes/google-ads-api-v22-sunset/ URL:https://adshift.co/changes/google-ads-api-v22-sunset/ CATEGORIES:Google TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-us-2026-political-ads-restriction-period@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261027 DTEND;VALUE=DATE:20261028 SUMMARY:Meta: Meta blocks new US ads about social issues\, elections or pol itics from Oct 27 to Nov 3 DESCRIPTION:Meta blocks new US ads about social issues\, elections or polit ics from Oct 27 to Nov 3\n\nWhat to do: If any client or brand runs ads in the social issues\, elections or politics category (including advocacy an d cause ads)\, get them approved and serving at least one impression befor e Oct 27\, 12:01am PT (3:01am ET)\, with final creative and targeting\, be cause you can't edit them after that. If your regular ads touch on topics Meta treats as social issues\, watch for them being flagged and held in re view this week.\n\nSource: https://developers.facebook.com/blog/post/2026/ 10/06/upcoming-2026-restriction-period-for-us-ads/\nDetails: https://adshi ft.co/changes/meta-us-2026-political-ads-restriction-period/ URL:https://adshift.co/changes/meta-us-2026-political-ads-restriction-perio d/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-commerce-order-management-api-shutdown@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261027 DTEND;VALUE=DATE:20261028 SUMMARY:[Action] Meta: Commerce Order Management API shuts down on every ve rsion Oct 27\, with no replacement DESCRIPTION:Commerce Order Management API shuts down on every version Oct 2 7\, with no replacement\n\nWhat to do: If your store or an app syncs nativ e Facebook or Instagram Shop orders\, confirm what breaks on Oct 27 and mo ve buyers to website checkout.\n\nSource: https://developers.facebook.com/ docs/graph-api/changelog/version26.0\nDetails: https://adshift.co/changes/ meta-commerce-order-management-api-shutdown/ URL:https://adshift.co/changes/meta-commerce-order-management-api-shutdown/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-delivery-estimate-fields-removed@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261027 DTEND;VALUE=DATE:20261028 SUMMARY:Meta: Three Delivery Estimate fields disappear from every API versi on on Oct 27 DESCRIPTION:Three Delivery Estimate fields disappear from every API version on Oct 27\n\nWhat to do: If a planning dashboard or forecasting tool draw s expected-results curves\, ask its owner whether it reads these fields an d what it will show after Oct 27.\n\nSource: https://developers.facebook.c om/docs/graph-api/changelog/version26.0\nDetails: https://adshift.co/chang es/meta-delivery-estimate-fields-removed/ URL:https://adshift.co/changes/meta-delivery-estimate-fields-removed/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-messenger-stories-placement-retired@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261027 DTEND;VALUE=DATE:20261028 SUMMARY:[Action] Meta: Messenger Stories ad placement retires DESCRIPTION:Messenger Stories is retired as an ad placement on every API ve rsion on Oct 27\n\nWhat to do: Remove "story" from messenger_positions in any manual-placement ad sets\, templates and bulk or agency scripts. Advan tage+ Placements need no action. After Oct 27\, compare delivery by placem ent with the week before.\n\nSource: https://developers.facebook.com/docs/ graph-api/changelog/version26.0\nDetails: https://adshift.co/changes/meta- messenger-stories-placement-retired/ URL:https://adshift.co/changes/meta-messenger-stories-placement-retired/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-poll-ads-deprecated@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261027 DTEND;VALUE=DATE:20261028 SUMMARY:[Action] Meta: Poll ads can no longer be created or updated on any version from Oct 27 DESCRIPTION:Poll ads can no longer be created or updated on any version fro m Oct 27\n\nWhat to do: Find any live poll ads and plan replacement creati ve. Ask tool vendors to strip poll fields from creative specs before Oct 2 7.\n\nSource: https://developers.facebook.com/docs/graph-api/changelog/ver sion26.0\nDetails: https://adshift.co/changes/meta-poll-ads-deprecated/ URL:https://adshift.co/changes/meta-poll-ads-deprecated/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-web-only-destination-web-app-campaigns@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261027 DTEND;VALUE=DATE:20261028 SUMMARY:Meta: Web-only destination creatives blocked in Website and App cam paigns from Oct 27 DESCRIPTION:Web-only destination creatives blocked in Website and App campa igns from Oct 27\n\nWhat to do: If you force web destinations inside Websi te and App campaigns\, switch to automatic destination selection or a comp atible manual destination before Oct 27.\n\nSource: https://developers.fac ebook.com/docs/graph-api/changelog/version26.0\nDetails: https://adshift.c o/changes/meta-web-only-destination-web-app-campaigns/ URL:https://adshift.co/changes/meta-web-only-destination-web-app-campaigns/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-product-browsing-default-on@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261028 DTEND;VALUE=DATE:20261029 SUMMARY:[Action] Meta: In-app product browsing turns on for existing Meta a ds DESCRIPTION:Meta turns on in-app product browsing for existing ads on Oct 2 8 unless you opt out\n\nWhat to do: Decide before Oct 28 whether you want this on. If not\, opt out\, or switch it off per ad\, and watch site sessi ons vs. Meta-reported conversions after the switch.\n\nSource: https://ppc .land/meta-will-turn-on-product-browsing-in-existing-ads-on-october-28/\nD etails: https://adshift.co/changes/meta-product-browsing-default-on/ URL:https://adshift.co/changes/meta-product-browsing-default-on/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:shopify-global-catalog-rest-api-shutdown@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261102 DTEND;VALUE=DATE:20261103 SUMMARY:Shopify: Global Catalog REST API shuts down DESCRIPTION:Shopify's Global Catalog REST API stops serving traffic on Nov 2\n\nWhat to do: Only matters if you or an app use Global Catalog. Confirm migration before Nov 2.\n\nSource: https://shopify.dev/changelog/global-c atalog-rest-api-stops-serving-traffic-on-november-2-2026\nDetails: https:/ /adshift.co/changes/shopify-global-catalog-rest-api-shutdown/ URL:https://adshift.co/changes/shopify-global-catalog-rest-api-shutdown/ CATEGORIES:Shopify TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-marketing-api-v24-sunset@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261110 DTEND;VALUE=DATE:20261111 SUMMARY:[Action] Meta: Marketing API v24.0 retires DESCRIPTION:Marketing API v24.0 is available until Nov 10\, 2026\n\nWhat to do: Make sure reporting tools\, bulk uploaders and agency scripts have mo ved to v25.0 or v26.0\, and check error logs after Nov 10.\n\nSource: http s://developers.facebook.com/docs/marketing-api/marketing-api-changelog\nDe tails: https://adshift.co/changes/meta-marketing-api-v24-sunset/ URL:https://adshift.co/changes/meta-marketing-api-v24-sunset/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-pixel-on-device-conversion-measurement-nov-12@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261112 DTEND;VALUE=DATE:20261113 SUMMARY:[Action] Meta: Meta Pixel starts measuring conversions on customer devices from Nov 12\, on by default DESCRIPTION:Meta Pixel starts measuring conversions on customer devices fro m Nov 12\, on by default\n\nWhat to do: Before Nov 12\, decide on purpose: check the toggle in Events Manager > Data sources > your Pixel > Settings and turn it off if you don't want it. Either way\, save a baseline now (d aily Meta-attributed purchases vs. Shopify paid orders for the last 30 day s)\, keep CAPI running\, and annotate Nov 12 in your reports so a jump in Meta ROAS isn't read as a performance win.\n\nSource: https://www.facebook .com/business/help/4237575203200036\nDetails: https://adshift.co/changes/m eta-pixel-on-device-conversion-measurement-nov-12/ URL:https://adshift.co/changes/meta-pixel-on-device-conversion-measurement- nov-12/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:google-data-manager-encrypted-customer-data@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261116 DTEND;VALUE=DATE:20261117 SUMMARY:Google: Data Manager switches from hashed to encrypted customer dat a DESCRIPTION:Google Ads Data Manager stops requiring SHA-256 hashed customer data on Nov 16 and switches to encryption\n\nWhat to do: List every Custo mer Match and offline-conversion upload that goes through Data Manager (CR M connectors\, scheduled file imports\, the API). Before Nov 16\, check wi th Google support or your rep whether your pre-hashed files keep working\, then compare match rates before and after the switch. Have privacy or leg al sign off on unhashed data being sent to Google's secure environment.\n\ nSource: https://ppc.land/google-ads-data-manager-stops-requiring-hashed-c ustomer-data-november-16/\nDetails: https://adshift.co/changes/google-data -manager-encrypted-customer-data/ URL:https://adshift.co/changes/google-data-manager-encrypted-customer-data/ CATEGORIES:Google TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:google-pmax-image-extraction-default-dec-4@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20261204 DTEND;VALUE=DATE:20261205 SUMMARY:[Action] Google: New PMax campaigns pull landing-page images by def ault DESCRIPTION:New Performance Max campaigns will pull images from your landin g pages by default from Dec 4\, even if you turned Dynamic images off\n\nW hat to do: If you turned Dynamic images off because of stock photos\, lice nsed or UGC imagery\, or regulated claims\, the account switch will no lon ger protect new PMax campaigns. From Dec 4\, set image extraction to Off o n each new Performance Max campaign you create. If you use a script or too l to build campaigns\, have it send GENERATE_IMAGE_EXTRACTION = OPTED_OUT. When you update an existing campaign through the API\, resend the whole a sset_automation_settings list\, because a partial update wipes the other s ettings (for example text automation). Check that your landing-page images are licensed for ads.\n\nSource: https://ads-developers.googleblog.com/20 26/10/upcoming-changes-to-image-extraction-in.html\nDetails: https://adshi ft.co/changes/google-pmax-image-extraction-default-dec-4/ URL:https://adshift.co/changes/google-pmax-image-extraction-default-dec-4/ CATEGORIES:Google TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:google-channel-prioritization-budget-allocation@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20270201 DTEND;VALUE=DATE:20270202 SUMMARY:Google: Display setup on Search campaigns changes (date given only as Feb 2027) DESCRIPTION:Google Ads adds channel priority and budget caps\, and the Disp lay setup on Search changes in Feb 2027\n\nWhat to do: Find Search campaig ns with Display Network on. To keep today's behavior after Feb 2027\, Goog le says to set Display to Low priority with a 50% budget allocation.\n\nSo urce: https://blog.google/products/ads-commerce/channel-prioritization-bud get-allocation/\nDetails: https://adshift.co/changes/google-channel-priori tization-budget-allocation/ URL:https://adshift.co/changes/google-channel-prioritization-budget-allocat ion/ CATEGORIES:Google TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:shopify-script-tags-deprecated@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20270301 DTEND;VALUE=DATE:20270302 SUMMARY:[Action] Shopify: Script tags stop running on storefronts DESCRIPTION:Shopify script tags stop running on storefronts on March 1\, 20 27\n\nWhat to do: Ask every app that adds code to your storefront whether it uses script tags\, and get migration dates. Test tracking pixels on a d uplicate theme well before March.\n\nSource: https://shopify.dev/changelog /online-store-script-tags-deprecation\nDetails: https://adshift.co/changes /shopify-script-tags-deprecated/ URL:https://adshift.co/changes/shopify-script-tags-deprecated/ CATEGORIES:Shopify TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT UID:meta-whatsapp-cloud-api-marketing-messages-sunset@adshift.co DTSTAMP:20261102T120538Z DTSTART;VALUE=DATE:20271013 DTEND;VALUE=DATE:20271014 SUMMARY:Meta: WhatsApp marketing messages leave the Cloud API DESCRIPTION:WhatsApp marketing messages stop working on the Cloud API on Oc t 13\, 2027 and must move to the Marketing Messages API\n\nWhat to do: If you send WhatsApp marketing to customers outside the US\, ask your messagi ng platform (Klaviyo\, Shopify Messaging\, or your WhatsApp provider) whet her it already sends marketing templates through the Marketing Messages AP I and when it will finish moving. If you run your own integration\, plan t he switch before April 2027 if you'll create new WhatsApp accounts\, and b efore Oct 13\, 2027 at the latest.\n\nSource: https://developers.facebook. com/blog/post/2026/10/21/sunsetting-marketing-messages-on-the-cloud-api/\n Details: https://adshift.co/changes/meta-whatsapp-cloud-api-marketing-mess ages-sunset/ URL:https://adshift.co/changes/meta-whatsapp-cloud-api-marketing-messages-s unset/ CATEGORIES:Meta TRANSP:TRANSPARENT END:VEVENT END:VCALENDAR