Crie um público personalizado de usuários que acessaram ou realizaram ações específicas no seu site usando o pixel da Meta, a API de Tag para JavaScript e as regras de público.
Depois de criar um público personalizado com dados do site, faça referência a ele para direcionar os anúncios da mesma forma que você faz com os públicos personalizados padrão. O Facebook atualiza esse público automaticamente de acordo com a política de retenção definida por você.
Consulte Custom Audience, Facebook Tag API e Rastreamento de conversão para saber mais.
Ao compartilhar eventos de conversão usando a API de Conversões, você pode criar um Público Personalizado do site para usar com anúncios. Você também pode criar um Público Personalizado offline e um Público Personalizado de aplicativo para celular. Recomendamos que você compartilhe o external_id
como um parâmetro de informações do cliente para melhorar as taxas de correspondência e impulsionar correspondências em diferentes canais.
O mapeamento de external_id
feito pela API de Conversões é diferente daquele usado com o extern_id
para criar um Público Personalizado de arquivo de cliente. O mapeamento de external_id
não pode ser usado para criar um Público Personalizado de arquivo de cliente. Da mesma forma, o extern_id
gerado por meio do mapeamento de Público Personalizado de arquivo de cliente não pode ser usado para criar Públicos Personalizados da web, offline nem de aplicativo para celular.
Para criar um Público Personalizado a partir de sites, você precisa aceitar os Termos de Serviço para Públicos Personalizados no Gerenciador de Anúncios.
Para criar um público personalizado do site, faça uma solicitação POST
para:
https://graph.facebook.com/v21.0
/act_<AD_ACCOUNT_ID>/customaudiences
Use os seguintes parâmetros:
Nome | Descrição |
---|---|
tipo: string | Obrigatório. Nome do público. |
tipo: objeto JSON | Obrigatório. Regras do público aplicadas à URL de referência. Consulte Regras de público. |
tipo: número inteiro | Opcional. Número de dias para manter alguém no público. Entre Se não for especificado, usaremos o valor |
tipo: booliano | Opcional. O padrão é
Se não for especificado, usaremos o valor |
Por exemplo:
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
Exemplo de resposta:
{ "id": "123567890" }
Um público personalizado para Públicos Personalizados de Site deve conter uma regra de público. Cada regra deve ser fornecida como uma cadeia de caracteres codificada por JSON. Consulte Regras de público para saber mais.
Use a chamada de API a seguir para criar um público personalizado de pixel:
curl -X POST \
-F 'name="My WCA Pixel"' \
-F 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/act_<AD_ACCOUNT_ID>/adspixels
A chamada retornará a identificação do pixel:
{ "id": "11111" }
Recupere o código de pixel do Público Personalizado:
curl -X GET \
-d 'fields="code"' \
-d 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<PIXEL_ID>/
A resposta a seguir será retornada, em que code
contém o código de pixel relevante para o público personalizado:
{ "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" } } }
Para ler públicos de uma conta de anúncios, faça uma solicitação HTTP GET
:
https://graph.facebook.com/v21.0
/act_<AD_ACCOUNT_ID>/customaudiences
Exemplo:
curl -X GET \
-d 'fields="id"' \
-d 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/act_<AD_ACCOUNT_ID>/customaudiences
Exemplo de resposta:
{ "data": [ { "name": "My Test CA", "id": "1234567890" }, { "name": "WCA", "id": "0987654321" }, ], }
Para ler um público personalizado específico:
curl -X GET \
-d 'fields="name,rule"' \
-d 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<CUSTOM_AUDIENCE_ID>/
Exemplo de resposta:
{ "name": "My WCA", "rule": "{\"and\": [\n\t\t{\"url\": {\"i_contains\": \"shoes\"}},\n\t\t{\"url\": {\"i_contains\": \"red\"}}]}", "id": "1234567890" }
Para atualizar o nome de um público personalizado:
curl -X POST \
-F 'name="Updated Name for CA"' \
-F 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<CUSTOM_AUDIENCE_ID>/
Exemplo de resposta:
{ "success": true }
Exclua um público por id
:
curl -X DELETE \
-F 'access_token=<ACCESS_TOKEN>' \
https://graph.facebook.com/v21.0/<CUSTOM_AUDIENCE_ID>/
Exemplo de resposta:
{ "success": true }
Este produto está obsoleto. Leia Públicos Personalizados do site aprimorados.
Permite que os anunciantes de viagens direcionem anúncios aos usuários que pesquisaram hotéis e voos com base na data de check-in. Por exemplo, o anunciante pode criar um público composto apenas por usuários com datas futuras de check-in.
Os anunciantes de viagens devem inserir a data de check-in no campo checkin_date para inicializações do pixel:
fbq('track', 'Search', {'checkin_date': '2015-09-15', 'num_of_travelers':2});
No momento, somente o formato ISO-8601 de data/hora é compatível. Por exemplo:
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)Onde:
YYYY
é o ano com quatro dígitosMM
é o mês com dois dígitos (01=janeiro etc.)DD
é o dia do mês com dois dígitos (01 a 31)hh
são os dois dígitos de hora (00 a 23: o sistema de horário de 12 horas NÃO é permitido)mm
são os dois dígitos de minutos (00 a 59)ss
são os dois dígitos de segundos (00 a 59)TZD
é o designador do fuso horário (+hhmm ou -hhmm)Os usuários que pesquisaram hotéis com start_date posterior ao dia de hoje nos últimos 30 dias:
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.