Nobeta Connect

Nobeta Connect is a companion plugin for Nobeta, a third-party advertising service (nobeta.com.br). It requires an active Nobeta account and a Token API; without a valid token the plugin cannot serve ads or manage your ads.txt. Install it, paste the Token API that Nobeta sent you and click Connect. From there the only decision left to you is how your /ads.txt should be handled. What it does: 1. Connects to Nobeta with your token. The plugin recognises which of your Nobeta sites this WordPress is and sets itself up. When it cannot tell for sure, it asks you to pick from a list. 2. Loads the Nobeta ad scripts automatically. There is nothing to paste and nothing to configure. Which ad formats appear on each page is decided by Nobeta. If your site already loads a Nobeta tag, the plugin does not add it a second time. 3. Handles your ads.txt, your way. You make one choice. Let Nobeta keep the file up to date, and the plugin takes it over and keeps it in sync for you. Or keep managing it yourself, and the plugin only shows you the lines to copy, writing the file when you click "Refresh lines". Nothing is written to your site until you choose and save. 4. Saves a backup before every change to your ads.txt. The ten most recent are kept, and you can download any of them from the plugin screen. Your own ads.txt lines If you work with other ad partners besides Nobeta, your own AdSense for example, those lines are safe. When you connect, the plugin reads the ads.txt you already have, learns which lines are yours, and keeps them on every update. When Nobeta publishes new lines Once a day the plugin checks whether there is anything new for your site. If there is, a notice appears on the Dashboard, the Plugins list and the Nobeta Connect screen. The check never changes your ads.txt by itself. If you manage the file yourself, nothing is applied until you click "Refresh lines". If you let Nobeta manage it, the new lines are applied for you and a backup is saved first. External services The plugin needs the Nobeta service to work. These are the calls it makes. Nobeta API, called by your site:

• https://adm.nobeta.com.br/api/listasites/<token>: finds out which Nobeta site this WordPress is. WHAT IS SENT: your Token API and your site address. WHEN: when you connect or save the token, and while the plugin is still finishing that step.
• https://adm.nobeta.com.br/api/adstxt/content/<token>: returns the Nobeta ads.txt lines for your site. WHAT IS SENT: your Token API and your site address. WHEN: when you connect or save the token, when you turn on automatic management, when you click "Refresh lines" or "Update now", while the Nobeta Connect screen is open, and once a day in the background.

WHAT IS STORED: your Token API, the site it resolved to, and, from the Nobeta response, the account holder name and the list of sites linked to your token. All of it is saved in this site's own settings and erased when you delete the plugin. Once a day Nobeta also asks your site whether new lines are pending. That question never changes what your site publishes and never touches your ads.txt on its own. Advertising scripts, loaded in your visitors' browsers once the site is connected:

• https://iab.nobeta.com.br/<site> and https://go.nobeta.com.br/<site>: the Nobeta ad tags.
• https://securepubads.g.doubleclick.net/tag/js/gpt.js: the Google Publisher Tag library, used by the Nobeta IAB tag.

Like any ad tag, these scripts may use the visitor's IP address, user agent and browsing context, and set cookies, in order to serve and measure ads. They load on your public pages while the site is connected. To stop them, click Disconnect on the Nobeta Connect screen, or deactivate the plugin. Service terms and privacy policies:

• Nobeta service: nobeta.com.br
• Nobeta privacy policy: nobeta.com.br/politica-privacidade
• Google terms of service: policies.google.com/terms
• Google privacy policy: policies.google.com/privacy

You, the site owner, are responsible for any cookie or consent notice (GDPR, LGPD and the like) required to run advertising on your site.

1. Install the ZIP from Plugins > Add New > Upload Plugin and activate.
2. Open Settings > Nobeta Connect, paste your Token API and click Connect. It worked when the connection card shows your site and the Ad scripts card confirms the Nobeta scripts are loading.
3. In the ads.txt card, pick "Let Nobeta keep my /ads.txt up to date" or "I want to manage my /ads.txt manually", then click Save changes. Nothing is written to your ads.txt until you choose.

If you do not have a token, contact Nobeta.

1.0.10

• Fixes the list of external services, which was showing up as a code box with a sideways scrollbar instead of readable text.

1.0.9

• The list of external services is easier to read: each address stands on its own instead of running into the next.
• New screenshot showing the screen for those who keep managing the ads.txt file themselves.

1.0.8

• The Nobeta and Google addresses on this page are clickable links now, instead of text you had to copy by hand.
• The list of what the plugin does is easier to read: each item stands on its own instead of running into the next.

1.0.7

• The screen that asks which of your sites this WordPress is now points to the right button: it says Connect, which is the button actually on screen at that moment.
• Documentation reviewed end to end against the plugin itself, so what the page describes is what the screens do.

1.0.6

• First release in the WordPress.org plugin directory.