If you searched for "ogads gpt builder" and wanted OpenAI's chatbot tool, this is a different thing: "GPT" here means Get Paid To. The OGAds GPT Builder is a tool in the OGAds publisher dashboard that creates a hosted, no-code Get Paid To (GPT) site, where users complete offers to earn rewards. You work in the GPT Sites tool. Before you start, you need an OGAds publisher account, a brand-new domain, and DNS managed on Cloudflare (a free Cloudflare account is enough), according to OGAds' launch blog post. OGAds has not published what the GPT Builder costs or whether it takes a share of revenue, so ask before you plan around it.
This guide follows OGAds' seven setup steps, covers the domain and email parts where beginners get stuck, and says which questions OGAds has not answered.
What the OGAds GPT Builder is
The GPT Builder is the product name. The tool you open in the dashboard is called GPT Sites. OGAds says it lets any publisher launch a working GPT site with no code and no hosting to manage.
A GPT site rewards users for simple tasks: installing and playing mobile games, trying apps, answering surveys or signing up for services. You name the site, pick one of three themes, fill in your branding, attach your own domain and connect email sending. Visitors then sign up, complete offers, earn "points or cash" and withdraw once they reach a payout threshold.
OGAds says the tool handles the hard parts behind the scenes: the offer feed, user accounts, reward tracking, and conversion verification through OGAds postbacks. Your job is to bring traffic.
What you need before you start
Check this list first:
- An OGAds publisher account. OGAds' terms say it reviews applications and generally replies within two business days. It can accept or reject an application at its sole discretion.
- A brand-new domain. OGAds' custom domain doc says you cannot use the same domain with a landing page or website.
- Cloudflare managing your domain's DNS, on the free plan. You can keep the domain at your registrar, such as Namecheap or GoDaddy, and point its nameservers to Cloudflare. You do not need to buy it from Cloudflare.
The OGAds terms also say a publisher must receive approval for each website or media outlet used with OGAds tools and campaigns. OGAds has not said whether a GPT site needs its own separate approval.
How to set up a Get Paid To site with the OGAds GPT Builder, step by step
These are the seven steps from OGAds' launch post, in its order. The post says the order matters: create the GPT site first, set up the domain, then assign it.
- Log in to your OGAds dashboard and open the GPT Sites tool.
- Create a new site. Give it a name, choose one of the three themes, and fill in your branding details. OGAds does not say what "branding details" includes.
- Set up your custom domain in the Custom Domains tool. The post says this step is required before your site can go live on its own address. The next section covers it, and DNS changes can take time to show.
- Assign your domain to the site. Once the domain is active, return to your GPT site and select it. If the domain does not show as active, the post says to give it time before troubleshooting.
- Connect email sending, so users get sign-up and account emails from your own domain.
- Customize the look with custom CSS, if you want to go beyond the default theme.
- Launch and drive traffic. The post names TikTok, YouTube, Instagram and Telegram.
Setting up the custom domain
This part rests on OGAds' general custom domain doc, which the launch post links for GPT sites. The doc is marked as updated about nine months ago and uses Content Lockers as its example. It never mentions GPT sites. Follow the numbering in the doc itself.
The doc asks you to do the following:
- Add your domain to Cloudflare on the free plan. Complete all the Cloudflare steps, including changing the nameservers at your registrar, until the site is added successfully.
- Set SSL to Flexible. The doc says you must pick Flexible in the SSL settings.
- Copy your account's record. In the OGAds dashboard, go to Tools → Custom Domains and click "Add Your Domain". OGAds shows a record specific to your account.
- Add a CNAME record in Cloudflare DNS with the value you copied. If the domain is brand new, the doc says you can delete the records already in the box.
- Enter your domain in the Custom Domains tool and click "Add Domain".
The doc does not give the CNAME's Name field or the proxy setting. The Google Doc it links as a more in-depth guide (a Google Doc, not an OGAds page) says to type "@" in the Name field and leave the proxy status unchanged, checked and orange.
Two things are not published. OGAds has not said whether a subdomain works, and its docs describe a separate Offerwall tool with a different, fixed CNAME target. No page links that tool to the GPT Builder, so use the account-specific record from the Custom Domains tool, as the launch post's link points you to.
Connecting email with Resend
A GPT site emails users for things like sign-ups and verification. OGAds says those emails should come from your own domain (for example, support@yourbrand.com), not a generic address. It calls an email sending service such as Resend "the easiest way" to do this. It does not call Resend the only way, and it has not said whether Resend is mandatory.
OGAds' steps:
- Create a free Resend account.
- Add your domain in Resend.
- Resend detects that your domain is on Cloudflare and opens a popup where you authorize the DNS changes. You do not copy records by hand.
- Once Resend verifies your domain, connect it to your GPT site's email settings.
OGAds has not described what the email settings contain beyond that.
Choosing a theme and styling with custom CSS
Every site starts from one of three themes. OGAds says each is mobile-friendly and ready to launch as it is, and all three can be restyled with CSS.
| Theme | Look | Layout notes (OGAds launch post) |
|---|---|---|
| 1 | Dark, green accent | Sidebar with Home, Earn, Withdraw and Profile pages; live earnings ticker across the top |
| 2 | Light, violet accent | Clean landing page, "Get started in 3 simple steps" section, trust badges |
| 3 | Dark, orange accent | High-contrast design with a grid of reward categories |
Every GPT site has a custom CSS field. The workflow is to paste your CSS into the field, save, and check your site. OGAds suggests having Claude write the CSS: open your site in your browser, paste OGAds' published prompt into Claude using the Claude browser extension, and let it work on the styling.
OGAds also published an example file as a GitHub gist (not a docs page). It adds these points:
- CSS is the only lever. You cannot edit HTML or JS.
- New CSS replaces the old CSS, so paste a full replacement instead of appending.
- Nine tokens drive the look:
--gptsite-primary,--gptsite-secondary,--gptsite-accent,--gptsite-background,--gptsite-surface,--gptsite-text,--gptsite-border,--gptsite-font-sansand--gptsite-radius. - Use
!importanton visual properties, even though custom CSS loads after the site's stylesheet. - The gist describes a template, and it says each install differs, so check the result on your own site.
Two details in OGAds' pages conflict. The launch post suggests swapping in a custom font, but the gist warns the platform may strip @import, so a font import may not work. The post also says "layout details" can change, while the gist says CSS is all you can edit. Plan on CSS only.
How the site earns and how you get paid
OGAds' model is simple. Every task on your site is an OGAds offer. When a user completes one, the advertiser pays you, and you share part of that payout with the user as their reward. The gap between what you earn and what you pay out is your margin. OGAds does not give the split. Treat any figure you see elsewhere as unconfirmed.
Two separate flows of money are involved.
Advertiser to publisher
These are OGAds' general publisher payment terms, not rules written for GPT sites. Each figure below names the OGAds docs page it comes from:
- The invoices doc says no invoices are created until you reach $50 in total earnings. It also says invoices are created weekly, by Tuesday morning, for the prior week's earnings.
- The payment terms doc says payments are processed on Net 7 or Net 30 terms, depending on the account. OGAds has not said which accounts get which.
- The payment processor doc says OGAds uses a third-party processor called Tipalti.
- The Payoneer doc says Payoneer has a $6 fee, and that your first invoice cannot be through Payoneer.
- The crypto doc says crypto is paid as USDC on the Ethereum blockchain, with a $15 fee.
- The early payment docs say early payments carry a 15% fee, and that OGAds cannot process any early payment if you have earned under $50.
The pages also disagree on payment methods. The OGAds homepage lists Crypto, PayPal, Wire, Direct Deposit and E-Cheque. The docs cover Payoneer, PayPal, ACH, wire and USDC. Do not treat either as a complete list. Ask OGAds which methods your account can use.
Publisher to user
OGAds has not published how this half works. It does not say who funds and sends user withdrawals, which methods exist, what the user payout threshold is, whether you can set reward rates or the threshold, or how identity checks (KYC) work. The launch post says only that users earn "points or cash" and withdraw at "a payout threshold". Points-to-cash conversion and fraud handling on user rewards are also unpublished.
Theme 3's demo screenshot shows text such as "instant gift cards & PayPal rewards" and "no payout minimums". That is placeholder copy on a demo site, not a promise about what the GPT Builder supports.
Getting visitors to your site
OGAds' launch post says to share your site on TikTok, YouTube, Instagram, Telegram, or wherever your audience already is. OGAds has not published a traffic guide for GPT sites, and no income figure for any channel exists to quote.
Each platform has its own rules about promotion, links and rewards, and you are responsible for following them. Do not use fake giveaways, "free gift card" lures, or any promise you cannot deliver to get clicks. They deceive visitors and can get your accounts removed.
What OGAds has not published
OGAds has not published the items below. Ask OGAds support about them before you commit time or money:
- Pricing for the GPT Builder, or any revenue share
- A limit on the number of sites
- Country or device restrictions (the pages say only "mobile-friendly")
- Whether subdomains work
- Whether other offerwalls can be added (OGAds says only that every task is an OGAds offer)
- Leaderboards, end-user referrals and SEO settings
- User payout methods, the user payout threshold, and whether rates or the threshold can be changed
- Points-to-cash conversion
- How KYC works
- Fraud handling and chargebacks on user rewards
- Whether Resend is mandatory and what the email settings hold
- Whether a GPT site needs separate approval
- Which accounts get Net 7 and which get Net 30
Where to learn more and what to do next
OGAds Learn has a GPT Builder course with two lessons: "Creating a Site" (09:33) and "Customization With Claude" (03:02). The launch post calls the course free, but the course page says it is only available to OGAds members and the lessons need a login. Expect to need an account.
Your next actions, in order:
- Get the domain active by following the custom domain doc.
- Assign the domain to your GPT site.
- Connect email from your own domain, for example through Resend.
- Style the site with custom CSS and check it on your phone and your computer.
- Plan how you will reach visitors within each platform's rules.
FAQ
Do I need to know how to code?
No code is needed to launch. OGAds says the tool needs no code and no hosting. Custom CSS is optional, and you cannot edit HTML or JS.
Do the Offerwall tool, aff_sub4 or the Postback URL apply to the GPT Builder?
OGAds has not said. Its offerwall doc covers a different tool (Tools → Offerwall), and no page links it to the GPT Builder. OGAds says the GPT Builder handles conversion verification through postbacks itself, and it gives no setup steps for them.
Can my site go live before I assign a domain?
OGAds' launch post says the custom domain step is required before your site can go live on its own address. Whether the site works at all before a domain is assigned is not published.