Details
-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Sustaining
-
Component/s: xOther
-
Labels:None
-
Environment:
Operating System: Linux
Platform: PC
Description
Fandango is running a campaign that includes Spanish words. One has an an accent:
pelĂcula
In sources this becomes:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1. row ***************************
id: 132420792
altKey: go253217s_pel%edcula
accountID: 131
siteID: 0
searchEngineAccountID: 35471
keywordID: 0
distributionID: 3
searchEngineIdentifier: 16842680
searchEngineGroupIdentifier: 1188318694
searchEngineMatchType: broad
searchEngineGroupID: 1715162
isBiddable: true
campaignID: 0
description: Keyword: [pel?cula] broad
type: 1
keyword: pel?cula
sourceURL:
cost: 0.2
maxCost: 0.2
waypointID: NULL
landingURL:
http://www.fandango.com/?sp=1&CMP=KNC-GBLB&refcd=GO253217S_pel%EDcula&tsacr=GO {creative}&hbx.cmp.c3=GO253217S_pel%EDcula%26tsacr=GO{creative}&es.pk=pel%EDcula&es.ou=50
passParams:
trackPerformance: true
searchEngineStatus: ok
searchEngineStatusText: Active
lastChecked: 0000-00-00 00:00:00
- 1. row ***************************
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Both the altkey and keyword reflect an error. The landing URL appears correct -
the character is encoded. We are getting search engine data for this based on
the searchEngineID I assume but matching up with the feed may prove impossible.
IN reporting the keyword appears as it does in the keyword field above.