반복 잠재고객 목록
컬렉션을 사용해 정리하기
내 환경설정을 기준으로 콘텐츠를 저장하고 분류하세요.
이 문서에서는 Google Analytics Data API v1의 고급 기능인 반복 잠재고객 목록을 설명합니다.
잠재고객 목록 내보내기 기능에 관한 소개는 잠재고객 내보내기 기본사항 가이드를 참고하세요.
반복되는 잠재고객 목록은 잠재고객 멤버십이 변경될 때마다 매일 잠재고객 목록을 생성하여 최신 데이터를 사용할 수 있도록 합니다.
일반 (반복되지 않는) 잠재고객 목록은 목록이 생성될 때 잠재고객에 있는 사용자의 정적 목록입니다.
매일 새 잠재고객 목록 만들기
하루의 시청자 데이터를 처리하고 멤버십을 업데이트하는 데 걸리는 시간은 일정하지 않습니다. 잠재고객 목록 데이터가 24시간 내에 업데이트된다고 확신할 수 있는 방법은 없습니다.
예를 들어 매일 같은 시간에 잠재고객 목록을 요청하더라도 어떤 날은 잠재고객 목록이 전날과 동일하고 어떤 날은 잠재고객 목록이 달라서 멤버십 변경이 하루 더 포함되어 있습니다.

잠재고객 목록은 최근 멤버십 변경 전날의 이벤트 데이터를 기반으로 합니다. 매일 멤버십 업데이트가 발생하기 전에 잠재고객 목록을 만들면 전날의 데이터가 사용됩니다. 일일 멤버십 업데이트가 발생한 후에 잠재고객 목록을 만들면 어제의 데이터가 사용됩니다.
반복되는 잠재고객 목록 주기적으로 폴링
반복되는 잠재고객 목록은 추가 하루의 데이터를 사용할 수 있을 때만 잠재고객 목록을 생성합니다. 이렇게 하면 새 잠재고객 목록을 만들 시기를 추측할 필요가 없습니다. 대신 하루 종일 반복되는 잠재고객 목록을 저렴하게 폴링하여 추가 데이터를 사용할 수 있는지 확인할 수 있습니다.

반복 잠재고객 목록 만들기
반복되는 잠재고객 목록을 만들려면 요청에서 RecurringAudienceList
객체를 사용하여 recurringAudienceLists.create
메서드를 호출합니다. 다음 매개변수가 필요합니다.
audience
필드의 유효한 잠재고객 이름으로 형식이 properties/{propertyId}/audiences/{audienceId}
입니다.
Google 애널리틱스 Admin API v1의 audiences.list
메서드를 사용하여 이 값을 가져올 수 있습니다. audiences.list
응답의 Audience.name
필드에는 잠재고객 이름이 포함됩니다.
dimensions
필드의 유효한 측정기준 목록입니다. 이 메서드에서 지원하는 측정기준 목록은 잠재고객 내보내기 스키마 문서를 참고하세요.
이 필드에 언급된 측정기준의 데이터만 잠재고객 목록에 포함됩니다.
다음은 반복되는 잠재고객 목록 생성 요청의 샘플입니다.
HTTP 요청
POST https://analyticsdata.googleapis.com/v1alpha/properties/1234567/recurringAudienceLists
{
"audience": "properties/1234567/audiences/12345",
"dimensions": [
{
"dimensionName": "deviceId"
}
]
}
recurringAudienceLists.create
메서드의 응답에는 name
필드에 이름 (예: properties/1234567/recurringAudienceLists/123
)이 포함되며, 이 이름은 후속 쿼리에서 이 반복 잠재고객 목록의 구성 메타데이터를 검색하는 데 사용할 수 있습니다. 또한 구성 메타데이터에는 이 반복되는 잠재고객 목록에 대해 생성된 잠재고객 목록 인스턴스의 리소스 이름이 포함됩니다.
HTTP 응답
{
"name": "properties/1234567/recurringAudienceLists/123",
"audience": "properties/1234567/audiences/12345",
"audienceDisplayName": "Purchasers",
"dimensions": [
{
"dimensionName": "deviceId"
}
],
"activeDaysRemaining": 180,
"audienceLists": [
"properties/1234567/audienceLists/45678"
]
}
recurringAudienceLists.get
메서드를 사용하여 특정 반복 잠재고객 목록에 관한 구성 메타데이터를 검색합니다. 구성 메타데이터에는 이 반복 잠재고객 목록에 대해 생성된 잠재고객 목록 인스턴스의 리소스 이름이 포함됩니다.
예를 들면 다음과 같습니다.
HTTP 요청
GET https://analyticsdata.googleapis.com/v1alpha/properties/1234567/recurringAudienceLists/123
RecurringAudienceList
인스턴스가 응답으로 반환됩니다. 이 반복 잠재고객 목록에 대해 생성된 잠재고객 목록 인스턴스의 리소스 이름을 포함하는 구성 메타데이터가 포함됩니다.
HTTP 응답
{
"name": "properties/1234567/recurringAudienceLists/123",
"audience": "properties/1234567/audiences/12345",
"audienceDisplayName": "Purchasers",
"dimensions": [
{
"dimensionName": "deviceId"
}
],
"activeDaysRemaining": 180,
"audienceLists": [
"properties/1234567/audienceLists/45678"
]
}
recurringAudienceLists.list
를 사용하여 속성의 모든 반복 잠재고객 목록을 나열할 수 있습니다.
Webhooks를 사용하여 새 잠재고객 목록에 관한 비동기 알림 수신
recurringAudienceLists.get
메서드를 사용하여 특정 반복 잠재고객 목록에 관한 구성 메타데이터를 주기적으로 폴링하는 대신 잠재고객 목록을 사용할 수 있게 되면 비동기식으로 Webhook 알림을 수신할 수 있습니다.
웹훅 알림을 구성하려면 새 반복 잠재고객 목록을 만들 때 webhookNotification
필드를 지정합니다.
Google 애널리틱스 Data API v1에서 Webhooks를 사용하는 방법에 관한 자세한 내용은 Async audience lists with webhooks
가이드를 참고하세요.
잠재고객 내보내기에서 사용자 가져오기
잠재고객 내보내기에서 사용자를 검색하려면 audienceExports.query
메서드를 호출하고 recurringAudienceLists.get
또는 recurringAudienceLists.list
에서 제공한 구성 메타데이터에서 검색된 잠재고객 내보내기 이름을 지정합니다.
HTTP 요청
POST https://analyticsdata.googleapis.com/v1beta/properties/1234567/audienceExports/123:query
잠재고객 내보내기가 준비되면 잠재고객의 사용자 목록이 포함된 응답이 반환됩니다.
HTTP 응답
{
"audienceExport": {
"name": "properties/1234567/audienceExports/123",
"audience": "properties/1234567/audiences/12345",
"audienceDisplayName": "Purchasers",
"dimensions": [
{
"dimensionName": "deviceId"
}
],
"state": "ACTIVE",
"beginCreatingTime": "2023-06-22T23:35:28.787910949Z"
},
"audienceRows": [
{
"dimensionValues": [
{
"value": "1000276123.1681742376"
}
]
},
{
"dimensionValues": [
{
"value": "1000374452.1668627377"
}
]
},
{
"dimensionValues": [
{
"value": "1000391956.1652750758"
}
]
},
{
"dimensionValues": [
{
"value": "1000410539.1682018694"
}
]
},
{
"dimensionValues": [
{
"value": "1000703969.1666725875"
}
]
}
],
"rowCount": 5
}
달리 명시되지 않는 한 이 페이지의 콘텐츠에는 Creative Commons Attribution 4.0 라이선스에 따라 라이선스가 부여되며, 코드 샘플에는 Apache 2.0 라이선스에 따라 라이선스가 부여됩니다. 자세한 내용은 Google Developers 사이트 정책을 참조하세요. 자바는 Oracle 및/또는 Oracle 계열사의 등록 상표입니다.
최종 업데이트: 2025-07-26(UTC)
[null,null,["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eRecurring audience lists automatically update daily with audience membership changes, providing access to the most recent data.\u003c/p\u003e\n"],["\u003cp\u003eThese lists are generated based on event data from one to two days prior, depending on the timing of daily membership updates.\u003c/p\u003e\n"],["\u003cp\u003eYou can poll a recurring audience list frequently to check for data updates or utilize webhooks for asynchronous notifications about new audience lists.\u003c/p\u003e\n"],["\u003cp\u003eTo create a recurring audience list, you need to specify the audience name and desired dimensions using the \u003ccode\u003erecurringAudienceLists.create\u003c/code\u003e method.\u003c/p\u003e\n"],["\u003cp\u003eRetrieving users in an audience export involves calling the \u003ccode\u003eaudienceExports.query\u003c/code\u003e method with the audience export name obtained from the recurring audience list's configuration metadata.\u003c/p\u003e\n"]]],["Recurring audience lists update daily with membership changes, unlike static, regular lists. To create one, use the `recurringAudienceLists.create` method, specifying a valid audience name and dimensions. These lists are updated when new data is available, and polling the list via `recurringAudienceLists.get` reveals if new data is present. Alternatively, webhooks can provide asynchronous notifications. Use `audienceExports.query` to retrieve users from an audience export based on the recurring audience lists.\n"],null,["# Recurring audience lists\n\nThis document describes recurring audience lists, which are an\nadvanced feature of the Google Analytics Data API v1.\nFor an introduction to the audience list export feature,\nsee the [audience export fundamentals guide](/analytics/devguides/reporting/data/v1/audience-export-basics).\n\nRecurring audience lists produce audience lists daily as\naudience memberships change, to ensure you're working with the most recent data.\n\nRegular (non-recurring) audience lists are static lists of users in the audience\nat the time the list is generated.\n\nCreate a new audience list daily\n--------------------------------\n\nIt takes a variable amount of time to process one day's audience data and update\nmembership. There's no way to be sure that the audience list data is updated in\n24 hours.\n\nFor example, even if you request an audience list at the same time each day,\non some days the audience list will be the same\nas the previous day, and on other days, the audience list will be different and\ncontain an additional day of membership changes.\n\nAudience lists are based on event data from one day before the most recent\nmembership changes. If you create an audience list before daily membership\nupdates occur, it will use data from the two days before. If you create an\naudience list after daily membership updates occur, it will use data from\nyesterday.\n\nPeriodically poll a recurring audience list\n-------------------------------------------\n\nRecurring Audience Lists only produce Audience Lists when an additional day's\ndata is available. This removes the guesswork of deciding when to create new\nAudience Lists. Instead, you can cheaply poll the Recurring Audience List\nthroughout the day to see if additional data is available.\n\nCreate a Recurring Audience List\n--------------------------------\n\nTo create a recurring audience list, call the\n[`recurringAudienceLists.create`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists/create)\nmethod using the\n[`RecurringAudienceList`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList)\nobject in a request. The following parameters are required:\n\n- A valid audience name in the [`audience`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList.FIELDS.audience) field, formatted as `properties/{propertyId}/audiences/{audienceId}`. You can use the [`audiences.list`](/analytics/devguides/config/admin/v1/rest/v1alpha/properties.audiences/list) method of the Google Analytics Admin API v1 to obtain this value. The [`Audience.name`](/analytics/devguides/config/admin/v1/rest/v1alpha/properties.audiences#Audience.FIELDS.name) field of the `audiences.list` response contains the audience name.\n- A valid list of dimensions in the [`dimensions`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList.FIELDS.dimensions) field. The list of dimensions supported by this method can be found in the [Audience Export Schema](/analytics/devguides/reporting/data/v1/audience-export-api-schema) documentation. Only the data for dimensions mentioned in this field is included in an Audience List.\n\nHere's a sample recurring audience list creation request: \n\n### HTTP Request\n\n POST https://analyticsdata.googleapis.com/v1alpha/properties/1234567/recurringAudienceLists\n {\n \"audience\": \"properties/1234567/audiences/12345\",\n \"dimensions\": [\n {\n \"dimensionName\": \"deviceId\"\n }\n ]\n }\n\nA response of the `recurringAudienceLists.create` method contains the\nname in the `name` field (such as\n`properties/1234567/recurringAudienceLists/123`), which can be used in\nsubsequent queries to retrieve the configuration metadata\nfor this recurring audience list. Also, the configuration metadata contains\n[resource names for audience list instances](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList.FIELDS.audience_lists)\ncreated for this recurring audience list. \n\n### HTTP Response\n\n {\n \"name\": \"properties/1234567/recurringAudienceLists/123\",\n \"audience\": \"properties/1234567/audiences/12345\",\n \"audienceDisplayName\": \"Purchasers\",\n \"dimensions\": [\n {\n \"dimensionName\": \"deviceId\"\n }\n ],\n \"activeDaysRemaining\": 180,\n \"audienceLists\": [\n \"properties/1234567/audienceLists/45678\"\n ]\n }\n\nPoll configuration metadata\n---------------------------\n\nUse the\n[`recurringAudienceLists.get`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists/get)\nmethod to retrieve configuration metadata about a specific\nrecurring audience list. The configuration metadata contains\n[resource names for audience list instances](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList.FIELDS.audience_lists)\ncreated for this recurring audience list.\n\nHere's an example: \n\n### HTTP Request\n\n GET https://analyticsdata.googleapis.com/v1alpha/properties/1234567/recurringAudienceLists/123\n\nAn instance of [`RecurringAudienceList`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList)\nis returned in response. It contains the configuration metadata, which includes\n[resource names for audience list instances](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList.FIELDS.audience_lists)\ncreated for this recurring audience list. \n\n### HTTP Response\n\n {\n \"name\": \"properties/1234567/recurringAudienceLists/123\",\n \"audience\": \"properties/1234567/audiences/12345\",\n \"audienceDisplayName\": \"Purchasers\",\n \"dimensions\": [\n {\n \"dimensionName\": \"deviceId\"\n }\n ],\n \"activeDaysRemaining\": 180,\n \"audienceLists\": [\n \"properties/1234567/audienceLists/45678\"\n ]\n }\n\nYou can use\n[`recurringAudienceLists.list`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists/list)\nto list all recurring audience lists for a property.\n\n### Use Webhooks to receive asynchronous notifications about new audience lists\n\nInstead of periodically polling the configuration metadata about a specific\nrecurring audience list using the\n[`recurringAudienceLists.get`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists/get)\nmethod, you can asynchronously receive Webhook notifications when an audience\nlist becomes available.\n\nTo configure Webhook notifications, specify the\n[`webhookNotification`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists#RecurringAudienceList)\nfield when creating a new recurring audience list.\n\nFollow the [`Async audience lists with webhooks`](/analytics/devguides/reporting/data/v1/audience-lists-webhooks) guide\nfor more information about using Webhooks in the Google Analytics Data API v1.\n\n### Retrieve users in an audience export\n\nTo retrieve users in an Audience Export, call the\n[`audienceExports.query`](/analytics/devguides/reporting/data/v1/rest/v1beta/properties.audienceExports/query)\nmethod and specify the Audience Export name\nretrieved from the configuration metadata provided by\n[`recurringAudienceLists.get`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists/get)\nor [`recurringAudienceLists.list`](/analytics/devguides/reporting/data/v1/rest/v1alpha/properties.recurringAudienceLists/list). \n\n### HTTP Request\n\n POST https://analyticsdata.googleapis.com/v1beta/properties/1234567/audienceExports/123:query\n\nIf the Audience Export is ready, a response containing the list of\nusers in an audience is returned: \n\n### HTTP Response\n\n {\n \"audienceExport\": {\n \"name\": \"properties/1234567/audienceExports/123\",\n \"audience\": \"properties/1234567/audiences/12345\",\n \"audienceDisplayName\": \"Purchasers\",\n \"dimensions\": [\n {\n \"dimensionName\": \"deviceId\"\n }\n ],\n \"state\": \"ACTIVE\",\n \"beginCreatingTime\": \"2023-06-22T23:35:28.787910949Z\"\n },\n \"audienceRows\": [\n {\n \"dimensionValues\": [\n {\n \"value\": \"1000276123.1681742376\"\n }\n ]\n },\n {\n \"dimensionValues\": [\n {\n \"value\": \"1000374452.1668627377\"\n }\n ]\n },\n {\n \"dimensionValues\": [\n {\n \"value\": \"1000391956.1652750758\"\n }\n ]\n },\n {\n \"dimensionValues\": [\n {\n \"value\": \"1000410539.1682018694\"\n }\n ]\n },\n {\n \"dimensionValues\": [\n {\n \"value\": \"1000703969.1666725875\"\n }\n ]\n }\n ],\n \"rowCount\": 5\n }"]]