オーディエンス エクスポートは、特定の時点でのオーディエンス内のユーザーのリストです。Data API を使用してオーディエンスのエクスポートを作成すると、そのオーディエンスのエクスポートは、リクエストの約 24 時間前のオーディエンス内のユーザーのスナップショットになります。Data API からのオーディエンス エクスポートは静的であるため、そのオーディエンスの最新データを表示するには、新しいオーディエンス エクスポートを作成する必要があります。
一方、Google 広告のリマーケティングでは、Google アナリティクスでオーディエンスのユーザーが自動的に Google 広告に継続的にエクスポートされるため、新しいオーディエンス データを手動でリクエストする必要はありません。
オーディエンスのエクスポートでは、常にユーザー ID でユーザーを識別し、次にデバイス ID で識別します。つまり、オーディエンスに関するレポートには、オーディエンス エクスポートの戻り値よりも多くのユーザーが表示される場合があります。たとえば、レポート用識別子が「デバイスベース」の場合、レポートではユーザー ID に基づいて重複が除去されませんが、オーディエンス エクスポートでは除去されます。
バックフィルの整合性
Google アナリティクスでオーディエンスを作成して Google 広告のリマーケティングを有効にすると、Google アナリティクスでは、最近追加されたメンバーに基づいて Google 広告の該当オーディエンスがバックフィルされます。ただし、Google アナリティクスのレポートとオーディエンス エクスポートには、バックフィルされたオーディエンスのメンバーは含まれません。Google アナリティクスのレポートとオーディエンス エクスポートでユーザーがそのオーディエンスに表示されるようにするには、オーディエンスの作成後にユーザーがイベントを記録する必要があります。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-07-26 UTC。"],[[["\u003cp\u003eAudience export data typically has a 24-hour freshness period, meaning recent user activity may not be reflected immediately.\u003c/p\u003e\n"],["\u003cp\u003eAudience exports provide a snapshot of users in an audience at a specific point in time, requiring new exports for updated data.\u003c/p\u003e\n"],["\u003cp\u003eAudience exports expire after 72 hours, necessitating daily updates to view the latest audience composition.\u003c/p\u003e\n"],["\u003cp\u003eUser limits exist for audience exports, potentially resulting in representative samples for large audiences or properties.\u003c/p\u003e\n"],["\u003cp\u003eAudience exports prioritize user ID and device ID for user identification, which can lead to discrepancies compared to Google Analytics reports using different reporting identities.\u003c/p\u003e\n"]]],["Audience export data has a 24-hour freshness, meaning recent user actions may take up to a day to appear. Exports are static snapshots, updated daily during daylight hours. Data expires after 72 hours, requiring daily new exports for the latest user list. User limits apply, providing samples in large audiences. Exports identify users by User ID then Device ID, differing from reporting identity settings. Backfilled memberships aren't included. User counts may differ between the UI and exports.\n"],null,["# Audience export data expectations\n\nThis guide explains important information about the data you see in audience\nexports.\n\nData freshness\n--------------\n\nAudience export data freshness is how long it takes Google Analytics\nto collect events, process events, and then update user membership\nin your audiences. For example, if that process takes 24 hours, then the\naudience export data freshness is 24 hours. For more information, see\n[Data Freshness](//support.google.com/analytics/answer/11198161).\n\nAudience export data freshness averages 24 hours. You might not see users\nin audience exports for events that took place less than 24 hours ago. For\nexample, if a user completes their first purchase, and then 7 hours\nlater you create an audience export for the \"Purchasers\" audience,\nyou likely won't see the user in that audience export. After 14 to 38 hours,\nit's likely you will see the user in new audience exports.\n| **Note:** We recommend only requesting an audience export once per day, per audience.\n\nAudience membership data is updated once per day, typically during\ndaylight hours in the property's timezone. This means that\naudience exports for the same audience at 9 AM and 11 AM will likely\nreturn the same data, but a new audience export later that day might include\nnew data, if your membership data is updated in the afternoon.\n\nAudience exports are snapshots\n------------------------------\n\nAudience exports are lists of users in an audience at a specific point in\ntime. When you create an audience export with the Data API, that audience export\nrepresents a snapshot of the users in that audience about 24 hours before you\nmade that request. Audience exports from the Data API are static, so you must\ncreate a new audience export to see the most recent data for that audience.\n\nIn contrast, for [Google Ads remarketing](//support.google.com/analytics/answer/9313634),\nGoogle Analytics automatically and continuously exports users in\naudiences to Google Ads, so you don't need to manually request new audience\ndata.\n\nData expiration\n---------------\n\nAudience exports expire after 72 hours. New users might enter and exit an\naudience each day. To view the latest users in an audience, you need to\ncreate new audience exports each day.\n\nUser limits\n-----------\n\nWhen the size of an audience or property exceeds a user limit,\naudience exports return representative samples of the audience.\n\nThese limits depend on your property type, for example a standard or\n360 property, and are enforced in each audience export request.\n\nReturned users are users in the requested audience, and considered\nusers are users that may or may not be a member of the audience.\n\n| Limit Type | Standard Property Limits | Analytics 360 Property Limits |\n|----------------------|--------------------------|-------------------------------|\n| Max returned users | 2 million | 200 million |\n| Max considered users | 10 million | 1 billion |\n\nReporting identity consistency\n------------------------------\n\n[Reporting identity](//support.google.com/analytics/answer/10976610)\ndecides how users are deduplicated in reports.\n| **Important:** Audience exports don't change based on the reporting identity setting.\n\nAudience exports always identify users by\n[user ID](//support.google.com/analytics/answer/9355972), then device ID.\nThis means\nthat reports on an audience can show more users than the\naudience export returns. For example, if the reporting identity is\n\"Device based\", then reports don't deduplicate based on user ID,\nbut audience exports do.\n\nBackfill consistency\n--------------------\n\nWhen you create an audience in Google Analytics and turn on Google Ads\nremarketing, Google Analytics\n[backfills that audience in Google Ads](//support.google.com/analytics/answer/9313634)\nwith recently added members. However, Google Analytics reports and\naudience exports don't contain backfilled audience memberships.\nA user must log an event after the audience is created for Google Analytics\nreports and audience exports to show the user in that audience.\n\nFor example, if a user logs a purchase event on June 20th, and you\ncreate a \"Purchasers\" audience on June 21st, then you likely need to\nwait until June 22nd to see that user in new audience exports. However, that\nuser will only be in the audience export if the user has logged any event on\nJune 21st.\n\nUser count reporting\n--------------------\n\nThe total user count displayed in the [Audience report](https://support.google.com/analytics/answer/12931462)\nand the [Audiences](https://analytics.google.com/analytics/web/#/?pagename=admin-audiences&utm_source=gahc&utm_medium=dlinks)\nmanagement page in the Google Analytics UI may differ from the number of users\nin an audience export.\n\nThe *total users* metric in the Google Analytics UI reports shows historical\naudience memberships at the time of the event, whereas an audience export\ncontains only memberships that haven't expired due to the audience membership\nduration setting.\n\nFor example, if the audience membership duration setting is 30 days, and you\nreport on audience total users in the Google Analytics UI over the last year,\nyou might observe 12 times more users in the Google Analytics UI versus in the\naudience export *(12 = 365/30)*."]]
