# VU Security — VU Security builds its LATAM demand engine on a trilingual site, programmatic SEO and measurable events. Services provided: UX/UI Design, Web Development, Content Strategy, Technical SEO & AEO, Growth Analytics. ## Meet VU Security VU Security is a LATAM digital identity company: identity verification, biometric authentication and real-time fraud detection, sold to banks, gaming operators, retailers, healthcare providers and governments across Argentina, Brazil, Chile, Colombia and Mexico. Its platform, VU ONE, consolidates three product lines behind one identity graph. VU came to Litebox with a mature product, an enterprise sales motion that worked, and a marketing site that produced almost none of it. ## The mission VU sells into a market where regulation starts the conversation. A compliance officer facing a new AML rule, a CISO after a fraud incident, a product lead replacing a vendor: each one arrives with a specific question about a specific country. VU's site answered none of them by name, its search traffic was almost entirely branded, and the leads that did arrive came in bursts nobody could trace back to a source. With this in mind, we defined the following project goals: - **Ship a marketing site in three languages** that speaks to Argentina, Brazil and the wider region as separate markets. - **Turn regulation into a search surface** so a compliance buyer can find the answer for their own regulator. - **Make every lead traceable** back to the page, campaign or event that produced it. - **Build a content engine the team can run** without a designer or a developer in the loop. ## The journey ### A trilingual site, shipped and instrumented We designed and built VU's marketing site from scratch and put it in production on 18 March 2026, in Spanish, English and Brazilian Portuguese. The contact form routes into Microsoft Dynamics by country, so a lead from Bogotá reaches the rep who covers Colombia. Instrumentation went in alongside the build rather than after it. That decision paid off in May, when our tracking audit found the "Request a demo" buttons on the homepage and every solutions page were firing no event at all. Every demo click from those pages had been invisible, and nobody knew. ### Regulation as a search surface The category name does not get searched. Terms like "identity verification software" and "KYC provider" return no measurable volume in Argentina, Mexico or Colombia, so a page aimed at the category would rank for nothing. What does get searched is the regulation: the law, the deadline, the document type, the regulator by name. So we built the layer underneath the category. Capability pages generated from VU's own product wiki, seven regulation pages for Argentina, a glossary and a fraud-types hub, and comparison pages the team edits from the CMS as competitors change. Each page ships with JSON-LD schema, an FAQ block and keywords validated against real search volume before a word gets written. The generator matters more than any single page. Pages come out of a template plus a data dictionary, which is what makes the next country a week of work instead of a quarter. ### Making events measurable VU's biggest lead spikes come from conferences, and none of them were tracked. Three spikes in 120 days, all landing as direct traffic on a generic contact page, indistinguishable from any other visit. We designed the fix as a repeatable cycle: one UTM convention per physical surface, QR codes generated per piece, a dedicated landing per event instead of the generic form, and a results report that compares one event against the next. FEBRABAN TECH 2026 was the first event to run on it. The landing shipped in three languages in 13 days, with an entry raffle as the lead magnet, and converted 31% of its visitors into leads. It also taught us the expensive part. The QR codes on the stand totems were made by VU without UTMs, so most of the traffic arrived unattributed. The rule that came out of it is now part of how we run events: send the client the QR codes, one per physical surface, before they build their own pieces. ## The outcome VU now has a site that a compliance buyer can navigate in their own language, a content system that produces pages without a designer, and the first events in the account's history that can be measured against each other. The engagement continues as a monthly retainer covering design, development, content and growth. Our impact looked like: - **A trilingual marketing site in production** in Spanish, English and Brazilian Portuguese since March 2026. - **A programmatic content engine** that turns product documentation and regulation into search-ready pages. - **Event attribution that did not exist before** with a landing template, a UTM convention and a per-event results report. - **A measurement layer the team trusts** after a tracking audit found the primary demo CTA firing no event at all. This project is a great example of how Litebox helps identity and security companies turn regulatory complexity into a demand channel. ## Project insights & FAQs ### What did Litebox deliver for VU Security? Litebox designed and built VU Security's marketing site in Spanish, English and Brazilian Portuguese, in production since March 2026, and runs its growth track under a monthly retainer. The work covers UX/UI design, web development, content strategy, technical SEO and AEO, and growth analytics, including the blog, programmatic content pages and event landings. ### How do you build a website for a company that sells in five countries? You treat each market as its own buyer, not as a translation. For VU Security that meant three languages, a contact form that routes leads to the sales rep who covers that country, and content organised around each market's own regulator rather than around the product catalogue. A single page translated three times answers the same question three times, which is not the same as answering three different questions. ### Why build regulation pages instead of product pages? Because in identity and fraud prevention, the category itself is not searched. Terms like "KYC provider" have no measurable volume in most of LATAM, while the specific law, deadline or document type does. Regulation pages meet the compliance buyer at the moment the question actually forms, and they carry a natural link into the product pages that answer it. ### How do you measure leads that come from a conference? By instrumenting the physical surfaces, not just the website. Each banner, totem, slide and flyer gets its own QR code and UTM, pointing at a landing built for that event instead of a generic contact form. Without that, event leads arrive as direct traffic and become impossible to separate from everything else, which is exactly where VU Security started. [Talk to the team](https://litebox.ai/contact-us) · [All case studies](https://litebox.ai/work) --- HTML version: https://litebox.ai/work/vusecurity · All pages: [sitemap.xml](https://litebox.ai/sitemap.xml) · Agent guide: [llms.txt](https://litebox.ai/llms.txt)