The FindWhat–Miva acquisition connected two jobs that merchants experience as one journey: bringing a prospective customer to a store and helping that person buy. The historical deal offers a useful way to examine where advertising, product information, checkout, and customer service hand responsibility to one another.
From a proposed deal to a completed acquisition
FindWhat announced plans to acquire Miva in September 2003. Its 2004 Form 10-K records the acquisition on January 1, 2004. FindWhat’s paid-search business and Miva’s commerce software brought customer acquisition and storefront operations into the same corporate group. This is a historical account of that transaction.
The strategic proposition is easy to understand: merchants need both a way to attract interested people and a place where those people can act. The filing documents the transaction and the businesses involved. Establishing the resulting benefit to a particular merchant would require evidence about that merchant’s implementation, costs, customers, and completed orders.
Follow one offer all the way through
Choose a real product and one advertised promise. Record the price, availability, eligible audience, destination, and intended action before reviewing a campaign. Then follow the path on a phone and a desktop. The point is to find changes in meaning as information moves between systems and teams.
On a small screen, scroll the table sideways to read all columns.
| Handoff | Question to answer | Owner’s evidence |
|---|---|---|
| Ad to product page | Does the destination show the item and terms that prompted the click? | Approved ad paired with the live product view. |
| Product to basket | Do the selected option, quantity, and price carry through? | A test basket with matching details. |
| Basket to checkout | Can the customer see the full applicable charges and correct mistakes? | A completed test, including error recovery. |
| Checkout to fulfillment | Does the confirmed order reach the team that supplies it? | Matching order reference and fulfillment record. |
| Customer to support | Can staff identify the offer and explain the next step? | A sample inquiry answered using the same terms. |
Make the records mean the same thing
Agree on the meaning of a completed order before comparing advertising and store reports. Write down which time zone, date range, cancellations, refunds, and test transactions each report includes. Keep order counts separate from revenue and margin. A merchant can receive more orders while earning less per order because the promotion or fulfillment costs changed.
Give each campaign a consistent identifier where the systems support it. Confirm that it survives the intended journey and that access to customer information follows the business’s permissions and retention practices. Resolve discrepancies with the smallest relevant set of records. A dashboard that combines different definitions can conceal the very handoff it is supposed to explain.
Diagnose the gap before buying more traffic
Fictional merchant example: A lamp advertisement promises a shade-and-base bundle. The landing page displays the bundle, but its button adds only the base to the basket. Visitors then ask support about the missing shade. The useful first response is to correct the basket behavior and retest the offer. Additional clicks would send more people through the same confusing journey.
Save the ad, product view, basket, and confirmation as one evidence set. After the repair, verify that the advertised item appears in fulfillment and that staff can explain its contents. Subsequent order data can then be interpreted with the implementation change clearly dated.
Use the merchant journey map to assign owners and document mismatches. The historical acquisition suggests why these functions belong in one conversation; the map helps a merchant coordinate them even when separate vendors supply the tools. For campaign planning, continue with the online marketing guide; for launch rehearsal, use campaign website readiness.