Meta 픽셀, JavaScript 태그 API 및 타겟 규칙을 사용하여 웹사이트를 방문했거나 웹사이트에서 특정 행동을 한 사용자의 맞춤 타겟을 만듭니다.
웹사이트 데이터로 맞춤 타겟을 만든 후에 표준 맞춤 타겟에서와 마찬가지로 광고 타게팅에서 맞춤 타겟을 참조합니다. Facebook은 설정된 잔류 정책에 따라 이러한 타겟을 자동으로 업데이트합니다.
자세한 내용은 맞춤 타겟, 타게팅, Facebook 태그 API 및 Meta 픽셀 통계를 참조하세요.
전환 API를 사용하여 전환 이벤트를 공유하면 웹사이트 맞춤 타겟을 만들어 광고에 사용할 수 있습니다. 오프라인 맞춤 타겟과 모바일 앱 맞춤 타겟도 만들 수 있습니다. external_id
를 고객 정보 매개변수로 공유하여 일치율을 높이고 채널 전체에서 매칭을 활용하는 것이 좋습니다.
전환 API를 통해 만든 external_id
매핑은 extern_id
로 고객 파일 맞춤 타겟을 만드는 데 사용한 것과 다릅니다. external_id
매핑은 고객 파일 맞춤 타겟을 만드는 데 사용할 수 없습니다. 마찬가지로 고객 파일 맞춤 타겟 매핑을 사용하여 만든 extern_id
는 웹 맞춤 타겟, 오프라인 맞춤 타겟 또는 모바일 앱 맞춤 타겟을 만드는 데 사용할 수 없습니다.
웹사이트에서 맞춤 타겟을 만들려면 광고 관리자에서 맞춤 타겟 서비스 약관에 동의해야 합니다.
웹사이트 맞춤 타겟을 만들려면 다음으로 POST
요청을 보냅니다.
https://graph.facebook.com/v21.0
/act_<AD_ACCOUNT_ID>/customaudiences
다음 매개변수를 사용합니다.
이름 | 설명 |
---|---|
유형: 문자열 | 필수 항목. 타겟 이름. |
유형: JSON 개체 | 필수 항목. 참조 URL에 적용된 타겟 규칙. 타겟 규칙을 참조하세요. |
유형: 정수 | 선택 사항. 사용자를 타겟으로 유지하는 기간(일). 지정하지 않으면 규칙의 |
유형: 부울 | 선택 사항. 기본값은
지정하지 않으면 규칙의 |
예를 들면 다음과 같습니다.
curl -X POST \
-F 'name="My Test Website Custom Audience"' \
-F 'rule={
"inclusions": {
"operator": "or",
"rules": [
{
"event_sources": [
{
"id": "<PIXEL_ID>",
"type": "pixel"
}
],
"retention_seconds": 8400,
"filter": {
"operator": "and",
"filters": [
{
"field": "url",
"operator": "i_contains",
"value": "shoes"
}
]
}
}
]
}
}' \
-F 'prefill=1' \
-F 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/act_<AD_ACCOUNT_ID>/customaudiences
응답 샘플:
{ "id": "123567890" }
웹사이트 맞춤 타겟의 맞춤 타겟에는 타겟 규칙이 포함되어야 합니다. 각 규칙은 JSON으로 인코딩된 문자열로 제공해야 합니다. 자세한 내용은 타겟 규칙을 참조하세요.
다음 API 호출을 사용하여 픽셀 맞춤 타겟을 만듭니다.
curl -X POST \
-F 'name="My WCA Pixel"' \
-F 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/act_<AD_ACCOUNT_ID>/adspixels
호출 결과에서 픽셀 ID가 반환됩니다.
{ "id": "11111" }
맞춤 타겟 픽셀 코드 검색:
curl -X GET \
-d 'fields="code"' \
-d 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<PIXEL_ID>/
그러면 다음 내용이 반환되고 code
에 관련 맞춤 타겟 픽셀 코드가 포함됩니다.
{ "data": [ { "code": "<script>(function() {\n var _fbq = window._fbq || (window._fbq = []);\n if (!_fbq.loaded) {\n var fbds = document.createElement('script');\n fbds.async = true;\n fbds.src = 'https://connect.facebook.net/en_US/fbds.js';\n var s = document.getElementsByTagName('script')[0];\n s.parentNode.insertBefore(fbds, s);\n _fbq.loaded = true;\n }\n _fbq.push(['addPixelId', '11111']);\n})();\nwindow._fbq = window._fbq || [];\nwindow._fbq.push(['track', 'PixelInitialized', {}]);\n</script>\n<noscript><img height=\"1\" width=\"1\" alt=\"\" style=\"display:none\" src=\"https://www.facebook.com/tr?id=11111&amp;ev=NoScript\" /></noscript>", "id": "11111" } ], "paging": { "cursors": { "before": "MjM4NzQ5Njk5NjI2Mzc2", "after": "MjM4NzQ5Njk5NjI2Mzc2" } } }
광고 계정의 타겟을 읽으려면 HTTP GET
요청을 보내세요.
https://graph.facebook.com/v21.0
/act_<AD_ACCOUNT_ID>/customaudiences
예:
curl -X GET \
-d 'fields="id"' \
-d 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/act_<AD_ACCOUNT_ID>/customaudiences
응답 샘플:
{ "data": [ { "name": "My Test CA", "id": "1234567890" }, { "name": "WCA", "id": "0987654321" }, ], }
특정 맞춤 타겟을 읽는 방법:
curl -X GET \
-d 'fields="name,rule"' \
-d 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<CUSTOM_AUDIENCE_ID>/
응답 샘플:
{ "name": "My WCA", "rule": "{\"and\": [\n\t\t{\"url\": {\"i_contains\": \"shoes\"}},\n\t\t{\"url\": {\"i_contains\": \"red\"}}]}", "id": "1234567890" }
맞춤 타겟 이름을 업데이트하는 방법:
curl -X POST \
-F 'name="Updated Name for CA"' \
-F 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<CUSTOM_AUDIENCE_ID>/
응답 샘플:
{ "success": true }
id
로 타겟을 삭제하는 방법:
curl -X DELETE \
-F 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<CUSTOM_AUDIENCE_ID>/
응답 샘플:
{ "success": true }
이 제품은 사용 중단되었습니다.향상된 웹사이트 맞춤 타겟을 참조하세요.
여행 업체 광고주가 사용자 체크인 날짜를 기반으로 호텔과 항공편을 검색한 사용자를 타게팅할 수 있습니다. 예를 들어 광고주는 체크인 날짜가 지나지 않은 사용자를 대상으로 타겟을 만들 수 있습니다.
여행 업체 광고주는 픽셀을 실행하려면 checkin_date 필드에 원하는 체크인 날짜를 입력해야 합니다.
fbq('track', 'Search', {'checkin_date': '2015-09-15', 'num_of_travelers':2});
현재는 ISO-8601 시간 형식만 지원합니다. 예를 들면 다음과 같습니다.
YYYYMMDD
(예: 20080921)YYYY-MM-DD
(예: 1997-07-16)YYYY-MM-DDThh:mmTZD
(예: 1997-07-16T19:20+0100)YYYY-MM-DDThh:mm:ssTZD
(예: 1997-07-16T19:20:30+0100)변수 설명:
YYYY
는 4자리로 된 연도입니다.MM
은 2자리로 된 월입니다(예: 01=1월).DD
는 2자리로 된 날짜입니다(01~31).hh
는 2자리로 된 시간 단위입니다(00~23)(am/pm은 허용하지 않음).mm
은 2자리로 된 분 단위입니다(00~59).ss
는 2자리로 된 초 단위입니다(00~59).TZD
는 표준 시간대 지정 부호입니다(+hhmm 또는 -hhmm).최근 30일 이내에 오늘 이후의 start_date에 대해 호텔을 검색한 사용자:
curl -F "name=search_hotel_later_than_today" -F "pixel_id=PIXEL_ID" -F "retention_days=30" -F 'rule={"event": {"i_contains": "search"}}' -F 'rule_aggregation={"type":"last_event_time_field", "config":{"field":"checkin_date", "time_format":"YYYY-MM-DD"}, "operator":"@&lt;", "value": "0"}' -F "access_token=ACCESS_TOKEN" "https://graph.facebook.com/API_VERSION/act_AD_ACCOUNT_ID/customaudiences"
With Custom Audiences, you can reach people who recently visited your website and deliver them highly relevant ads based on interest they express in your products.
Other benefits include:
By tracking how each customer progresses in a process, you can more effectively influence customers who expressed interest in your products. For example, using Meta Pixel, capture intent based on activity of people who are viewing pages about a loyalty program, browsing a particular product page, or filling out a preferences form. Later, you can serve relevant ads to these people to help them complete the conversion.
See Advertiser Help Center, Custom Audience from your Website. When you add or remove people, updates can take a few hours. But your ads continue to run.
At this time, there's a maximum of 10000
Custom Audiences from your website that can be created in a single account.
Yes. Exclusion targeting prevents a particular audience from seeing your ad to help deliver your advertising more precisely. For example, exclude an audience of your current customers if you run a campaign to acquire new customers.
In Ads Manager, in the audience section of creating an ad, click Exclude and add the custom audience to the list.
The longest duration can be set for 365 days
. After 365 days, audience members are removed, unless they revisit the website again and match the same audience rule.
Yes. Open Ad Manager. Under the Audiences tab, click the New Audience drop-down menu and select Lookalikes.
Dating can use Custom Audiences from your website. However, gambling websites must be approved through the sales team on a managed list, and you must provide demographic restrictions, such as 21 years+.
We recommend CPM bidding for Website Custom Audience until your audience has reached a sufficiently large size. Start with CPM, then migrate to oCPM
or CPC
once you reach sufficient scale.
Yes, Custom Audiences from your website works with all native ad formats and serves across desktop, mobile, and tablet.
FBX
and Website Custom Audiences are complementary products. FBX
is best when advertisers require product-level dynamic ads, which are as current as possible and are not yet easily facilitated by Custom Audiences from your website. However, FBX is limited to desktop inventory. Custom Audiences from your website allows targeting across browsers, overlaying of Meta data, access to mobile inventory, and usage of all Meta ad units—all of which are not available on FBX
.
Custom Audiences from Your Website requests a duration where customers will be retained within the audience created. The duration is based on when customers visited a website and fired the Meta Pixel. For example, with a retention window of 30 days, if someone visits a website and matches an Audience rule on June 1st, Facebook automatically removes them from the Website Custom Audience on June 30.
You can create rules based on URLs visited or on custom events from Meta Pixel. Using custom data, create audiences based upon SKUs, Pricing, Color, or any other attribute you send to Facebook. See Meta Pixel.
No personal information is reported to the advertiser about any individual person on a website. You can only target an audience once it reaches a certain size; it's impossible to learn the individual identity an any person visiting a website.
Meta also provides an AdChoices link where people can learn more and opt out of targeted ads they receive. Click the “x” in the top-right corner of ads to show more options:
savings.att.com
or att.com
, or the page facebook.com/ATT
if we have it. Block the sub-domain or page across ad accounts.View Tags are not yet permitted for Custom Audiences from your website clients. Only Atlas view tag are accepted at this time.
Yes, it's possible to share Website Custom Audiences.
If an Active
campaign targets a Website Custom Audience and that audience is deleted, the campaign is put on Pause
.
We update an audience as soon as technically possible. Once customers go to webpages with a Meta Pixel and match an Audience rule, they're added to that Website Custom Audience. If this Website Custom Audience is being targeted with an ad, the customer is eligible to be served an ad in a matter of minutes.
No. There's one Meta Pixel generated per account. Add this Meta Pixel to all pages of your website one at a time, and use Audience rules to create different Website Custom Audiences.
Yes. You can use data from third-party tags, Tag Managers, or a DFA Floodlight tag. This depends on the sophistication of the third-party client. Simple rules are easy to implement, but if you pass dynamic variables through the JavaScript event, your third-party tag should receive them and pass them to the Meta Pixel via Custom Data fields.
The full JavaScript version has the following advantages over the IMG-only pixel:
A pixel ID is an identifier of the piece of code placed on an advertiser's website. There's one pixel ID per Meta Ad account.
In your rules, refer to event names under the parameter 'event'. For rules based on custom data, refer to it the same way you do for referring URLs, under the parameter 'url'. For example, to matches all visitors:
"filter": { "operator": "or", "filters": [ { "field": "url", "operator": "i_contains", "value": "signup" } { "field": "event", "operator": "i_contains", "value": "SignUp" } ] }
The following rule matches all visitors who have viewed any product in the TV category by fbq.push(['track', 'ViewProduct', {category: 'TV'}]);.
"filter": { "operator": "or", "filters": [ { "field": "event", "operator": "i_contains", "value": "ViewProduct" } { "field": "category", "operator": "i_contains", "value": "TV" } ] },
The above examples shows how to track remarketing events. Use the same way to track conversion events by replacing eventName
with conversion ID. This ID is created during the regular conversion creation flow (https://www.facebook.com/ads/manage/convtrack.php).
window.fbq = window.fbq || []; fbq.push(['track', 123456, {currency: 'USD', value: 30.00}]);
Ideally, you don't need to know whether a fired event is a conversion event or a remarketing event. You only need the conversion ID to fire a conversion event. For example, if the old conversion pixel is:
var fb_param = {}; fb_param.pixel_id = '1234567890'; fb_param.value = '5.00'; fb_param.currency = 'USD'; (elided other code)
Then, using the new pixel, it is the following:
window.fbq = window.fbq || []; fbq.push(['track', 1234567890, {currency: 'USD', value: 5.00}]);
The old conversion pixel allowed either a conversion pixel or a remarketing pixel on a page. Meta Pixel allows multiple pixel firings, including multiple conversion events, multiple remarketing events, or both per page.
Manually insert an IMG
tag:
<img height="1" width="1" border="0" alt="" style="display:none" src="https://www.facebook.com/tr?id=pixel_ID/ad_account_id&ev=event name&cd[p1]=v1&cd[p2]=v2..." />
Custom data is represented as key-value pairs. Each parameter is inside 'cd[...]'. For example:
<img height="1" width="1" border="0" alt="" style="display:none" src="https://www.facebook.com/tr?id=1234&ev=ViewProduct &cd[category]=TV" />
Is equivalent to the following JS call:
window.fbq = window.fbq || []; fbq.push(['track', 'ViewProduct', {category: 'TV'}]);
Use parameter 'ev' to specify conversion ID, parameter 'cd[value]' to specify value, and parameter 'cd[currency]' to specify currency:
<img height="1" width="1" border="0" alt="" style="display:none" src="https://www.facebook.com/tr?id=1234&ev=1234567890 &cd[value]=5.00&cd[currency]=USD" />
Meta Pixel code tries to fire events using JavaScript first. If JavaScript isn't available, Meta Pixel code tries to use image pixel. However it's recommended to always use the JavaScript pixel:
HTTP GET
limit in sending custom data.