Angaben zum Datum
Datum aus der Quelle.
Erstmals gesehen am .
Linkedin Marketing API von Linkedin
LinkedIn Marketing API: Legacy Geo entfällt ab 31. August 2026
Ab dem 31. August 2026 unterstützt LinkedIn Legacy Geo im Ads Targeting nicht mehr (Anfragen zur Kampagnenerstellung liefern einen 400-Fehler mit INVALID_VALUE_FOR_FIELD, stattdessen ist Bing-geo zu verwenden), das Feld location wird aus den Antworten von /v2/me und /v2/people entfernt (Ersatz: geoLocation), und in Version 202607 liefert die Predictive Audiences API nun das schreibgeschützte Feld id zurück sowie die Conversions API einen neuen Identifier für das Matching.
The top-level location field (for example, "San Francisco Bay Area") is also being removed from /v2/me and /v2/people responses. Partners currently relying on location may begin receiving an empty or null value and should migrate to the geoLocation field (for example, request projection=(geoLocation(geo~,autoGenerated))), which is already available on both endpoints. See the Profile API documentation for guidance on using geoLocation with the geo~ projection to retrieve the location display name.
July 2026 - Version 202607
Product & Platform Announcements
Predictive Audiences API: id field available in the response:
Starting version
202607, fetching a Predictive Audience (single or list) now returns its read-onlyid. Partners can now obtain theidfor audiences created in Campaign Manager or the API, and use it to update them.Conversions API: New user identifier available for matching: …