---
title: "Buy Website Traffic South Africa: Buy Targeted Traffic"
canonical: "https://froggyads.com/buy-website-traffic-south-africa/"
markdown_url: "https://froggyads.com/buy-website-traffic-south-africa.md"
description: "Plan buy website traffic south africa with South Africa targeting, source controls, creative tests, verified tracking, budget limits and accepted campaign."
language: "en"
---

Official-source campaign procurement brief

# Buy Website Traffic South Africa

Create South African traffic cells only after the served location and language path, accountable electronic transaction, POPIA roles, ZAR checkout, Africa/Johannesburg clock, and accepted source outcome are documented.

[Create My Free Account](https://premium.froggyads.com/#/signup)[Explore South Africa Traffic Buying](https://froggyads.com/buy-south-africa-traffic/)Country or portfolio evidence ·Reversible source controls ·No guaranteed outcomes

![buy website traffic south africa planning visual](https://froggyads.com/assets-redesign-2026/images/v97-colombia-chile-peru-south-africa-traffic-evaluation/buy-website-traffic-south-africa-hero.svg)

**On this page**

- [Evidence boundary](https://froggyads.com/buy-website-traffic-south-africa/#v12-evidence-buy-website-traffic-south-africa)

- [Campaign scope](https://froggyads.com/buy-website-traffic-south-africa/#buy-website-traffic-south-africa-direct-answer)

- [Offer route](https://froggyads.com/buy-website-traffic-south-africa/#za-offer)

- [Data roles](https://froggyads.com/buy-website-traffic-south-africa/#za-data)

- [Source ledger](https://froggyads.com/buy-website-traffic-south-africa/#za-measurement)

- [Questions](https://froggyads.com/buy-website-traffic-south-africa/#za-faq)

## Evidence boundary for Buy Website Traffic South Africa

Buying website traffic in South Africa should be treated as a source-level experiment with an accountable data and merchant path. The [South African Information Regulator](https://inforegulator.org.za/popia/) publishes POPIA material on information-officer responsibilities and personal-information processing. It provides a regulatory reference, not approval of a campaign, audience, landing page or payment method. For example, the advertiser can isolate one South African location, language, device, placement and ZAR route, then retain the source ID through consent state, submitted action and accepted backend record. Name the responsible party, operator, purpose, necessary fields, recipients and retention before tags are released. Separately test seller identity, offer terms, customer assistance, checkout success, rejection and refund handling. The campaign ledger should distinguish technical events from commercially accepted outcomes and keep Africa/Johannesburg aligned with UTC. Expand only a source cell whose full customer journey can be replayed and whose matured cost remains inside the written loss limit.

Reviewed by the FroggyAds Editorial Team for South African source, ZAR journey and POPIA evidence boundaries.

Direct answer

## What does Buy Website Traffic South Africa require?

Buy Website Traffic South Africa means funding a small acquisition cell after location and language fit, supplier and electronic-transaction facts, POPIA responsibility, direct-marketing choice where relevant, ZAR checkout, Africa/Johannesburg timing, and accepted-event reconciliation have passed. Government acts define review boundaries. They do not certify an advertiser or guarantee users, sales, or return.

Decision summary

## Four release conditions before meaningful spend

- Define the actual province, city, service footprint, audience language, device, and offer before using the national GEO.

- Name the responsible party and operator for every campaign-data route instead of treating the media platform as the universal owner.

- Rehearse the ZAR transaction, confirmation, failure, reversal, complaint, and refund paths with permission.

- Separate page, data, payment, and support failures from source evidence before excluding South African delivery.

Service cell

## Specify the South African location, audience language, and operational promise

A national selection is not evidence that the advertiser can serve every South African user. Create a cell record for the province or city, service or delivery coverage, product eligibility, audience language, device, support hours, price basis, payment route, cancellation or return handling, and complaint owner. Test the complete destination and assistance route in that context.

If the campaign uses English or another language, document why it fits the defined audience and verify the creative, page, form or checkout, confirmation, errors, material notices, and support. Do not convert national diversity into an invented language rule or an assumed audience preference.

| Area | Evidence to verify | Decision rule |
|---|---|---|
| Location | Province, city, service footprint | Exclude unsupported areas |
| Journey | Audience language through support | Test material meaning |
| Operations | ZAR, payment, fulfilment, complaint | Assign accountable owners |

**Connect the guide to live testing**

## Connect Buy Website Traffic South Africa to a controlled audience test

Use the choices established in “Specify the South African location, audience language, and operational promise” to define one audience, budget and source set in FroggyAds. Keep the surrounding offer and measurement rule stable so the test adds evidence to buy website traffic south africa instead of mixing several changes at once.

[Create My Free Account](https://premium.froggyads.com/#/signup)

![Illustration of audience targeting controls for a buy website traffic south africa test](https://froggyads.com/assets-redesign-2026/images/showcase-audience-targeting.svg)

Electronic transaction

## Version the South African supplier, offer, and digital commitment route

The Electronic Communications and Transactions Act governs covered electronic communications and transactions and includes consumer-protection provisions. Use the current consolidated text and qualified interpretation to review the supplier identity, product or service, material conditions, price and currency, payment, delivery or service, cancellation, confirmation, contact, complaint, and support on the actual route.

Preserve the page and terms version, approval owner, test date, and any exception. When the supplier, recurring condition, charged amount, delivery boundary, or complaint channel changes, reopen the electronic transaction review. A generic law citation cannot certify the updated offer.

![buy website traffic south africa controlled workflow visual](https://froggyads.com/assets-redesign-2026/images/v97-colombia-chile-peru-south-africa-traffic-evaluation/buy-website-traffic-south-africa-workflow.svg)

POPIA roles

## Assign a responsible party and operator before South African data moves

POPIA provides personal-information processing conditions, rights, an Information Regulator, direct-marketing provisions, automated-decision context, and cross-border-flow rules. Map click identifiers, cookies, device attributes, audience lists, form values, CRM fields, postbacks, analytics, fraud signals, vendors, and foreign recipients to the responsible party and each operator.

Record purpose, processing ground, notice, minimization, accuracy, security, retention, deletion, access or correction handling, direct-marketing choice where applicable, and transfer review. Remove an optional data element when nobody can explain the operational purpose or accept responsibility for its safeguards.

ZAR checkout

## Prove the merchant path rather than inferring South African payment capability

Record the amount shown, named ZAR or other currency, unavoidable fee, accepted method, authentication, failure message, retry, confirmation, settlement evidence, reversal, refund, and support route for the exact merchant and device. National payment availability or a payment logo cannot prove that this offer works for the targeted user.

Align checkout, support, technical receipt, duplicate window, and backend acceptance with Africa/Johannesburg. Retain the advertising account zone when it differs. Do not classify a platform conversion as commercially accepted until the advertiser can join it to the record used for order, lead, subscription, or revenue decisions.

![buy website traffic south africa evaluation scorecard visual](https://froggyads.com/assets-redesign-2026/images/v97-colombia-chile-peru-south-africa-traffic-evaluation/buy-website-traffic-south-africa-scorecard.svg)

**Choose the execution format**

## Choose a paid-media format that supports Buy Website Traffic South Africa

Use the criteria around “Prove the merchant path rather than inferring South African payment capability” to decide whether push, native, display or pop fits the message and destination. Set format, targeting and spend as campaign controls in FroggyAds while the buy website traffic south africa decision remains the standard for judging the result.

[Create My Free Account](https://premium.froggyads.com/#/signup)

![Illustration comparing advertising formats for buy website traffic south africa execution](https://froggyads.com/assets-redesign-2026/images/showcase-ad-formats.svg)

Failure attribution

## Adjudicate South African sources with a layered incident ledger

Create separate incident states for destination availability, language mismatch, offer drift, POPIA uncertainty, identifier loss, payment failure, duplicate receipt, backend rejection, cancellation, complaint, refund, and later-value loss. Attach the responsible system, owner, evidence, and next test so one symptom does not automatically become a traffic-quality verdict.

Use FroggyAds controls to keep the cell small and reversible. A source moves among keep, observe, reduce, pause, and retest only after compatible cohorts mature. No GEO, source filter, device setting, or quality signal guarantees a person, intention, compliant processing, accepted customer, or profitable outcome.

Entity evidence

## Named concepts supported by this page

### South Africa website traffic campaign

A South Africa website traffic campaign is a controlled acquisition cell with POPIA responsibility mapping, electronic-transaction review, verified language and service coverage, ZAR checkout evidence, and accepted source outcomes.

### POPIA responsibility map

POPIA responsibility map identifies the responsible party, operator, purpose, processing ground, notice, security, retention, rights, direct-marketing handling, and cross-border flow for campaign data.

### South African electronic transaction review

South African electronic transaction review checks the accountable supplier, offer, price, currency, payment, delivery or service, cancellation, complaint, confirmation, and support on the live digital route.

### ZAR checkout evidence

ZAR checkout evidence records displayed and charged currency, required fees, payment method, authentication, settlement, failure, reversal, refund, and accepted-record continuity for the merchant path.

### Africa Johannesburg event timing

Africa Johannesburg event timing aligns delivery, support, transaction, technical receipt, deduplication, and backend maturity with the named IANA zone instead of an assumed offset.

Query fan-out

## Page-specific research phrases

- buy website traffic south africa

- south africa popia traffic

- south african electronic transaction review

- zar checkout traffic test

- africa johannesburg event timing

- south africa source outcome audit

- prepare a south africa traffic cell under popia

- verify an electronic transaction route in south africa

- test a zar checkout before buying website visits

- schedule acquisition with africa johannesburg records

- separate south africa source quality from checkout failure

**Put the guide into practice**

## Turn Buy Website Traffic South Africa into a bounded campaign test

With “Named concepts supported by this page” documented, launch only the next reversible test. Set a spending limit, preserve the baseline and use source-level and audience controls so the next step depends on qualified outcomes for buy website traffic south africa, not activity volume.

[Create My Free Account](https://premium.froggyads.com/#/signup)

![Illustration of a campaign launch checklist for buy website traffic south africa](https://froggyads.com/assets-redesign-2026/images/showcase-campaign-launch-checklist.svg)

Tier A operator record

## Twelve release controls for Buy Website Traffic South Africa

### ZA 01 · served location boundary

South African control 01 isolates served-location boundary: province or city, service footprint, product eligibility, delivery or performance conditions and exclusions are stated. In this review, the campaign file distinguishes a geographic selection from evidence that the offer can be fulfilled there. Record 01 assigns a served-location-boundary reviewer, a served-location-boundary observation time, a served-location-boundary route version and a served-location-boundary source boundary for South Africa.

Evidence response 01 for served-location boundary requires that the campaign file distinguishes a geographic selection from evidence that the offer can be fulfilled there. Its bounded action is to remove unsupported South African locations before the next delivery decision. The served-location-boundary log 01 preserves the served-location-boundary device, the served-location-boundary owner, the served-location-boundary exception and the served-location-boundary retest condition in the South African file.

### ZA 02 · audience language route

South African control 02 isolates audience-language route: the selected language is reviewed across creative, terms, transaction, confirmation, errors, privacy information and support. In this review, one versioned route shows whether meaning survives every consequential customer step. Record 02 assigns a audience-language-route reviewer, a audience-language-route observation time, a audience-language-route route version and a audience-language-route source boundary for South Africa.

Evidence response 02 for audience-language route requires that one versioned route shows whether meaning survives every consequential customer step. Its bounded action is to do not replace complete language evidence with a broad country assumption. The audience-language-route log 02 preserves the audience-language-route device, the audience-language-route owner, the audience-language-route exception and the audience-language-route retest condition in the South African file.

### ZA 03 · supplier responsibility

South African control 03 isolates supplier responsibility: supplier, offer owner, contact, price owner, fulfilment owner, complaint owner and terms version are verified. In this review, the responsibility file connects each promise with an operator who can correct or honour it. Record 03 assigns a supplier-responsibility reviewer, a supplier-responsibility observation time, a supplier-responsibility route version and a supplier-responsibility source boundary for South Africa.

Evidence response 03 for supplier responsibility requires that the responsibility file connects each promise with an operator who can correct or honour it. Its bounded action is to pause when accountability becomes ambiguous anywhere on the South African route. The supplier-responsibility log 03 preserves the supplier-responsibility device, the supplier-responsibility owner, the supplier-responsibility exception and the supplier-responsibility retest condition in the South African file.

### ZA 04 · electronic commitment

South African control 04 isolates electronic commitment: amount, currency, required fees, payment, recurring condition, confirmation, cancellation and complaint handling are rehearsed. In this review, screens and backend records from the same digital commitment provide the decision evidence. Record 04 assigns a electronic-commitment reviewer, a electronic-commitment observation time, a electronic-commitment route version and a electronic-commitment source boundary for South Africa.

Evidence response 04 for electronic commitment requires that screens and backend records from the same digital commitment provide the decision evidence. Its bounded action is to open a fresh review after a material change to the electronic route. The electronic-commitment log 04 preserves the electronic-commitment device, the electronic-commitment owner, the electronic-commitment exception and the electronic-commitment retest condition in the South African file.

### ZA 05 · POPIA role map

South African control 05 isolates POPIA role map: responsible party, operators, purposes, processing ground, notices, rights, security and retention are assigned for campaign data. In this review, the map identifies where each field enters and which accountable role can answer for its use. Record 05 assigns a POPIA-role-map reviewer, a POPIA-role-map observation time, a POPIA-role-map route version and a POPIA-role-map source boundary for South Africa.

Evidence response 05 for POPIA role map requires that the map identifies where each field enters and which accountable role can answer for its use. Its bounded action is to remove data that has no documented purpose or responsible owner. The POPIA-role-map log 05 preserves the POPIA-role-map device, the POPIA-role-map owner, the POPIA-role-map exception and the POPIA-role-map retest condition in the South African file.

### ZA 06 · direct-marketing choice

South African control 06 isolates direct-marketing choice: the team determines whether the activity is covered outreach and preserves the relevant identity, basis, record and opt-out handling. In this review, choice evidence is tested through the actual audience and suppression workflow. Record 06 assigns a direct-marketing-choice reviewer, a direct-marketing-choice observation time, a direct-marketing-choice route version and a direct-marketing-choice source boundary for South Africa.

Evidence response 06 for direct-marketing choice requires that choice evidence is tested through the actual audience and suppression workflow. Its bounded action is to stop the affected channel while its permission or exclusion state remains unresolved. The direct-marketing-choice log 06 preserves the direct-marketing-choice device, the direct-marketing-choice owner, the direct-marketing-choice exception and the direct-marketing-choice retest condition in the South African file.

### ZA 07 · cross-border data route

South African control 07 isolates cross-border data route: vendors and foreign recipients are listed with fields received, purpose, safeguard review, deletion route and incident owner. In this review, the diagram follows the South African campaign record through every external handoff. Record 07 assigns a cross-border-data-route reviewer, a cross-border-data-route observation time, a cross-border-data-route route version and a cross-border-data-route source boundary for South Africa.

Evidence response 07 for cross-border data route requires that the diagram follows the South African campaign record through every external handoff. Its bounded action is to review a new recipient and its route before any transfer begins. The cross-border-data-route log 07 preserves the cross-border-data-route device, the cross-border-data-route owner, the cross-border-data-route exception and the cross-border-data-route retest condition in the South African file.

### ZA 08 · ZAR merchant rehearsal

South African control 08 isolates ZAR merchant rehearsal: the merchant's displayed ZAR or stated currency route is tested through charge, authentication, confirmation, settlement, reversal and refund. In this review, device evidence and backend records establish what this merchant actually supports. Record 08 assigns a ZAR-merchant-rehearsal reviewer, a ZAR-merchant-rehearsal observation time, a ZAR-merchant-rehearsal route version and a ZAR-merchant-rehearsal source boundary for South Africa.

Evidence response 08 for ZAR merchant rehearsal requires that device evidence and backend records establish what this merchant actually supports. Its bounded action is to avoid inferring checkout readiness from payment infrastructure available elsewhere. The ZAR-merchant-rehearsal log 08 preserves the ZAR-merchant-rehearsal device, the ZAR-merchant-rehearsal owner, the ZAR-merchant-rehearsal exception and the ZAR-merchant-rehearsal retest condition in the South African file.

### ZA 09 · Johannesburg evidence clock

South African control 09 isolates Africa/Johannesburg maturity: delivery, support, payment, postback and backend events are aligned to the Africa/Johannesburg cohort boundary. In this review, late arrivals and duplicates stay visible until the acceptance window closes. Record 09 assigns a Africa-Johannesburg-maturity reviewer, a Africa-Johannesburg-maturity observation time, a Africa-Johannesburg-maturity route version and a Africa-Johannesburg-maturity source boundary for South Africa.

Evidence response 09 for Africa/Johannesburg maturity requires that late arrivals and duplicates stay visible until the acceptance window closes. Its bounded action is to hold the source decision until local chronology and mature records reconcile. The Africa-Johannesburg-maturity log 09 preserves the Africa-Johannesburg-maturity device, the Africa-Johannesburg-maturity owner, the Africa-Johannesburg-maturity exception and the Africa-Johannesburg-maturity retest condition in the South African file.

### ZA 10 · South Africa outcome join

South African control 10 isolates accepted-event join: campaign and source identifiers connect to a deduplicated event accepted under the advertiser's declared business rules. In this review, rejections, cancellations, refunds and later value remain part of the South African source record. Record 10 assigns a accepted-event-join reviewer, a accepted-event-join observation time, a accepted-event-join route version and a accepted-event-join source boundary for South Africa.

Evidence response 10 for accepted-event join requires that rejections, cancellations, refunds and later value remain part of the South African source record. Its bounded action is to release spend from mature acceptance rather than a convenient front-end event. The accepted-event-join log 10 preserves the accepted-event-join device, the accepted-event-join owner, the accepted-event-join exception and the accepted-event-join retest condition in the South African file.

### ZA 11 · layered incident queue

South African control 11 isolates incident ownership: service, language, electronic transaction, data, checkout, tracking and backend failures receive separate owners. In this review, the incident record names the affected cell, containment step, corrective evidence and retest condition. Record 11 assigns a incident-ownership reviewer, a incident-ownership observation time, a incident-ownership route version and a incident-ownership source boundary for South Africa.

Evidence response 11 for incident ownership requires that the incident record names the affected cell, containment step, corrective evidence and retest condition. Its bounded action is to do not let success in one layer conceal an unresolved fault in another. The incident-ownership log 11 preserves the incident-ownership device, the incident-ownership owner, the incident-ownership exception and the incident-ownership retest condition in the South African file.

### ZA 12 · contained South Africa step

South African control 12 isolates controlled expansion: one audience, source, creative, bid or budget dimension changes after the reference cohort matures. In this review, marginal accepted cost and quality are compared with the last defensible South African setting. Record 12 assigns a controlled-expansion reviewer, a controlled-expansion observation time, a controlled-expansion route version and a controlled-expansion source boundary for South Africa.

Evidence response 12 for controlled expansion requires that marginal accepted cost and quality are compared with the last defensible South African setting. Its bounded action is to roll back the newest increment if its stated limit is crossed. The controlled-expansion log 12 preserves the controlled-expansion device, the controlled-expansion owner, the controlled-expansion exception and the controlled-expansion retest condition in the South African file.

Frequently asked questions

## Buy Website Traffic South Africa FAQ

### What should be defined before buying website traffic in South Africa?

Define the served province or city, audience language, device, offer eligibility, support route and measurable outcome before launch. This keeps the first campaign cell narrow enough to verify whether the destination and service promise fit the people being targeted.

### How can an advertiser verify location fit for a South African campaign?

Test the complete journey for the actual service or delivery area instead of treating a national setting as proof of coverage. Record any province, city or eligibility limits, then confirm that the landing page, checkout and customer assistance reflect them.

### Why does audience language need its own campaign check?

The selected language should remain clear across the creative, landing page, form or checkout, confirmation, errors and material notices. Document why it fits the intended audience, and avoid assuming that one language represents every South African user.

### What should be reviewed on a South African digital offer?

Review the accountable supplier, product or service, material terms, price and currency, payment, delivery or performance, cancellation, contact and complaint route on the actual page. Reopen that review whenever a material part of the offer changes.

### How should campaign data responsibilities be documented?

Map the responsible party and each operator for click identifiers, cookies, form fields, analytics, fraud signals, postbacks and CRM records. Record the purpose, necessary fields, recipients, safeguards, retention and handling of relevant user requests before optional data is collected.

### What payment evidence is useful for South African traffic?

Verify the displayed and charged currency, unavoidable fees, accepted method, authentication, failure message, confirmation, settlement evidence, reversal, refund and support route for the exact merchant and device. A payment logo alone does not prove that the journey works.

### How should event timing be handled in the campaign record?

Keep delivery, support, transaction and backend acceptance times aligned with the Africa/Johannesburg time zone, while preserving the advertising account time zone when it differs. This makes duplicate windows, delayed outcomes and reporting cutoffs easier to reconcile.

### Which outcome should determine whether a source is retained?

Use the advertiser's accepted backend event rather than relying on a page visit or platform conversion alone. Preserve the source identifier through consent, submission and acceptance so each source can be judged against the same commercial rule.

### How can poor traffic be separated from a broken customer journey?

Log destination availability, language mismatch, offer drift, identifier loss, payment failure, backend rejection, cancellation, complaint and refund as separate states. Attach the responsible system and next test before treating one symptom as evidence about traffic quality.

### When is a South African traffic cell ready to expand?

Expand only after location, language, offer, data route, payment path and accepted outcomes remain aligned through a meaningful observation period. Increase exposure in controlled steps, keep the written loss limit active and pause when the evidence can no longer be replayed.

Related regional resources

## Continue the South Africa traffic workflow

[**South Africa Website Traffic**Continue with a related South Africa traffic planning and measurement resource.](https://froggyads.com/south-africa-website-traffic/)[**South Africa Traffic Source**Continue with a related South Africa traffic planning and measurement resource.](https://froggyads.com/south-africa-traffic-source/)[**Buy Traffic From South Africa**Continue with a related South Africa traffic planning and measurement resource.](https://froggyads.com/buy-traffic-from-south-africa/)[**Push Traffic South Africa**Continue with a related South Africa traffic planning and measurement resource.](https://froggyads.com/push-traffic-south-africa/)Controlled evidence release

## Build the first South Africa evidence cell

Advance the South Africa cell only while location, language, supplier, POPIA, ZAR transaction, clock, and accepted-outcome records remain aligned.

[Create My Free Account](https://premium.froggyads.com/#/signup)[Visit Learning Center](https://froggyads.com/learning-center/)

Search intent and buyer decision

## How to use this Buy Website Traffic South Africa page

This URL has one primary job for **performance-focused advertisers**: **plan the market-specific test and measurement rules**. Keep this page focused on that buying decision instead of turning it into a generic advertising article. The nearest related FroggyAds page is [South Africa Website Traffic](https://froggyads.com/south-africa-website-traffic/); use that URL when its narrower task is the one you actually need. For the Buy Website Traffic South Africa decision, apply this rule to plan the market-specific test and measurement rules and keep the evidence tied to this page's specific buyer task.

The current competitor review for this page records 10 reviewed comparison and competitor pages in the general ads cluster, with 10 fetched successfully. Separately, the page-level entity coverage tracks campaign objective, audience, ad format, budget, bid, conversion tracking, and source quality. We use both as coverage checks, not as copied claims or proof of FroggyAds performance. For the Buy Website Traffic South Africa decision, apply this rule to plan the market-specific test and measurement rules and keep the evidence tied to this page's specific buyer task.

| Step | Geo workflow | Evidence to retain |
|---|---|---|
| 1 | Verify market eligibility, language and offer fit | Keep the evidence tied to Buy Website Traffic South Africa and the accepted outcome defined for this URL. |
| 2 | Hold targeting and measurement rules stable for the first market test | Keep the evidence tied to Buy Website Traffic South Africa and the accepted outcome defined for this URL. |
| 3 | Scale only when market-level accepted economics remain healthy | Keep the evidence tied to Buy Website Traffic South Africa and the accepted outcome defined for this URL. |

### Transparent Buy Website Traffic South Africa decision example

**Hypothetical example:** if a controlled Buy Website Traffic South Africa test spends USD 225 and records 8 accepted outcomes after the same review window, accepted CPA is USD 225 divided by 8 = **USD 28.12**. Replace the example inputs with your own economics; this is not a FroggyAds performance claim.

Use FroggyAds as the execution layer only when the page's decision calls for paid traffic. Set the relevant budget, targeting and format controls, verify conversion tracking, keep source-level evidence, and increase spend only when the accepted outcome supports the next step. [Create your free FroggyAds account](https://premium.froggyads.com/#/signup). For the Buy Website Traffic South Africa decision, apply this rule to plan the market-specific test and measurement rules and keep the evidence tied to this page's specific buyer task.

Direct answer

## Buy Website Traffic South Africa — what matters first

Buy Website Traffic South Africa should be evaluated market by market: define eligible geography, keep measurement consistent, and scale only where accepted-outcome economics remain viable.