There's a line in nearly every eSIM provider's support documentation that reads something like: "If your data isn't working after installation, try entering the APN settings manually." The APN is the Access Point Name — a configuration string that tells your phone which network gateway to route data through. On a physical SIM, this is set automatically by the carrier. On a poorly implemented travel eSIM, it's your problem.
Truely does not have that support article. This piece explains why — and what the technical difference actually is.
What Is an APN and Why Does It Matter
When your phone connects to a mobile network, it establishes a data connection through a specific gateway on the carrier's network. That gateway is identified by the APN. The APN string typically looks something like "internet.carrier.com" or "broadband." Different carriers use different APNs. Some carriers use different APNs for different plan types on the same network.
On a domestic SIM card that came with your phone plan, this is configured automatically during activation. The SIM card contains a carrier-specific configuration that includes the correct APN, and your phone reads it without any user input.
On a travel eSIM from most providers, the configuration is more generic. The profile specifies a default APN that works with some carriers in some countries. When it doesn't work — because the carrier at your destination uses a different APN format — data silently fails. The network bars show full signal. The data icon appears. Nothing loads.
This is the single most common cause of the one-star review pattern you see for eSIM products across the App Store and Google Play. "Showed full bars, no data." It's not a coverage problem. It's an APN configuration problem.
How Truely Embeds Configuration at the Profile Level
Truely's eSIM profiles are carrier-specific, not generic. When Truely negotiates a bilateral agreement with a carrier in a given country, part of that agreement is technical: the carrier provides the exact APN configuration required for data routing on their network. Truely embeds that configuration directly into the eSIM profile that users download.
The result is a profile that, for each carrier network it might connect to, already contains the correct APN. When your device registers on the Docomo network in Japan, for example, the profile already has Docomo's APN pre-configured. No manual entry. No lookup. No support ticket.
This requires maintaining a live database of carrier APN configurations across every network in Truely's coverage map, updating it when carriers change their infrastructure, and embedding the current version of that database in every new eSIM profile issued. It's an engineering maintenance burden that adds ongoing operational cost — but it's the cost of the product actually working without user intervention.
The Provisioning Handshake
The APN configuration is half the picture. The other half is plan activation — the moment when the carrier's billing system recognizes that a given eSIM profile has an active paid plan and should be allowed to route data.
In a typical travel eSIM product, this happens in one of two ways. Either the plan is activated at the time of purchase and remains active for the plan duration regardless of whether the user is traveling (burning days they aren't using), or the plan activates when the user manually triggers it through the provider's app.
Truely uses a third approach: carrier-triggered automatic activation. When your device registers on a partner carrier network — specifically when the carrier's HLR (Home Location Register) sends a location update for your device — Truely's provisioning system receives that signal and automatically marks the plan as active for that session. The plan clock starts when you land, not when you buy.
This behavior is governed by the provisioning API specifications in Truely's carrier contracts. Not all carriers support this capability — it requires the carrier to provide a registration webhook endpoint. Part of Truely's carrier vetting process is confirming that the technical infrastructure for automatic activation is in place before signing an agreement. That's one reason Truely's carrier count is lower than some providers who list any carrier with eSIM roaming as "supported."
What Happens When Your Phone Switches Carriers
In countries with multiple carrier agreements — like the US, Germany, or Australia — your device might connect to different carriers depending on where you are. A Truely plan in the US might route through T-Mobile in an urban area and AT&T in a rural area, depending on signal strength and roaming agreements.
Each time your device hands off to a different carrier, the APN configuration needs to match that carrier's requirements. Truely's multi-carrier profile handling addresses this through carrier-priority ordering: the profile contains a priority list of carriers for each covered country, and the APN configuration for each carrier in that list. When the device switches, the correct APN switches with it.
This is transparent to the user. You drive from Berlin into Bavaria, your device moves between carriers, and the data connection continues uninterrupted. The technical complexity is real — but the user experience is simple.
Why Not Just Use the Same APN Everywhere
Some eSIM providers solve the APN problem differently: they operate their own MVNO (Mobile Virtual Network Operator) and route all traffic through a single APN on their own infrastructure, which then connects to partner carriers. This architecture allows a single, consistent APN across all destinations.
The tradeoff is latency and cost. MVNO routing adds one network hop. For a data packet originating in Tokyo, routing through an MVNO gateway in London before reaching its destination adds measurable latency — typically 40–80ms depending on the gateway location. For web browsing, this is barely perceptible. For video calls, it can degrade quality during peak usage periods. For trading platforms or real-time applications, it matters more.
Truely's architecture uses direct carrier routing rather than MVNO intermediation. Your data traffic goes to the local carrier and from there to the internet, with no intermediate hop. The APN complexity this creates is handled on Truely's infrastructure side, not the user's device side.
The Support Ticket Volume Difference
Truely tracks the support ticket category breakdown by issue type on a weekly basis. Across the past six months, the category "data not working after installation" accounts for less than 3% of inbound tickets. For context, that same category represents 22–35% of inbound ticket volume for the two largest competitor eSIM products based on publicly available App Store review analysis.
The gap is explained almost entirely by the APN pre-configuration and automatic activation systems described above. Users who don't have to configure anything don't file tickets about configuration failures.
The remaining 3% of "data not working" tickets at Truely fall into two sub-categories: devices with outdated carrier settings that need an iOS or Android update before the eSIM profile works correctly, and destinations where a partner carrier had an outage. Neither of these is solvable through Truely's architecture — they're third-party infrastructure issues. But they represent a much smaller and more bounded problem space.
What Installation Actually Looks Like
On iPhone, the process goes like this: you receive an email from Truely with a QR code attached. You open Settings > Mobile Data > Add eSIM. Your camera opens. You scan the QR code. A confirmation dialog appears. You tap "Add." The profile installs in about 60 seconds. You see "Truely" appear in your carrier list alongside your home carrier.
You don't select an APN. You don't enable data roaming for the eSIM profile. You don't configure anything. When you land and your phone connects to the local network, data starts working. The screen shows the local carrier name in the status bar. Your Truely plan is active.
On Android, the process is marginally more varied because device manufacturers implement eSIM settings in different menu locations. On Samsung, you go to Settings > Connections > SIM card manager > Add eSIM. The rest of the process is the same. Google Pixel follows an identical flow. Other Android manufacturers use similar but slightly different navigation paths — the QR scan step is consistent across all of them.
Reinstallation After a Factory Reset
One scenario where user action is required: factory resets. An eSIM profile is stored on the device's eUICC chip, but a factory reset wipes the chip. The profile is gone. To get it back, you need to reinstall it.
Truely handles this with a one-tap reinstall request through the Truely app or the support portal. You submit the request, Truely's provisioning system generates a new QR code tied to the same plan, and you reinstall using the same process as the original installation. The turnaround time for a reinstall request is under 30 minutes during business hours and typically under two hours at night.
Most users never encounter this scenario. For the ones who do — traveling with a new phone, or after a software emergency — the process is straightforward and the existing plan is preserved without requiring a new purchase.